POST
EntriesSettings.Remove
Remove an entry/tab setting definition. Alias of EntriesSettings.Delete. Hard-deletes the tabs_setting row, same as the dashboard trash icon. It does not set status=0.
Permissions
- User must be logged in with a valid bearer token.
- The user must be from the same company domain as the request Host (call the API on that account subdomain or allowed custom domain). A token from another company returns success=0, error user_not_in_company.
- Returned or changed records are limited by the user permissions, team access, folder access, and account settings.
Action
- Removes one entry/tab definition from settings.
- The removed id should no longer be offered as an entry_id in the UI after User.Basic refreshes.
Push Service
No row-level socket push is sent because this function changes entry settings, not entry row data.
Automation
No business automation is run for entry settings changes.
Special Instructions
- On a company subdomain (e.g. https://{user_domain}.bull36.com) the user must match that Host — Login and protected APIs reject another company with success=0, error user_not_in_company. On a main brand host (bull36.com, biz1.co.il, mastrocrm.com, …) the company domain gate is skipped.
- Use EntriesSettings.Remove or EntriesSettings.Delete; both DELETE the tabs_setting row.
- This matches dashboard Tab_setting::delete_tab_setting_data. status=0 is not used because status is the JSON status map.
- To remove one row inside a selected tab, use Entries.Remove or Entries.Delete with entry_id and row id.
- After removing settings, call User.Basic again so the UI refreshes the available entries list.
Required Parameters
| Name | Type | Sample | Explanation |
|---|---|---|---|
idpost | int | 7 | Entry/tab id to remove. |
Optional Parameters
No optional body parameters are defined for this function.
Authentication
Send the bearer token returned by Login in the request header. The user must be from the same company domain as this Host — a token from another company is rejected (user_not_in_company).
Authorization: Bearer YOUR TOKEN
Sample Request
{
"url": "\/app\/EntriesSettings.Remove",
"method": "POST",
"headers": {
"Authorization": "Bearer YOUR TOKEN"
},
"body": {
"id": "7"
},
"url_user": "https:\/\/{user}.bull36.com\/app\/EntriesSettings.Remove",
"url_domain": "https:\/\/{domain}\/app\/EntriesSettings.Remove"
}Endpoint
POST /app/EntriesSettings.Remove
POST https://{user}.bull36.com/app/EntriesSettings.Remove
POST https://{domain}/app/EntriesSettings.RemoveSample Output
{
"success": 1,
"id": "7",
"message": "Record removed successfully."
}JavaScript Example
const token = 'YOUR TOKEN';
const body = new URLSearchParams();
// Fill body fields from the Sample Request JSON above.
const res = await fetch('/app/EntriesSettings.Remove', { method: 'POST', headers: { Authorization: 'Bearer ' + token }, body });
const data = await res.json();
console.log(data);Error Example
{
"success": 0,
"message": "Record was not found."
}