POST
EntriesSettings.Update
Update an entry/tab setting definition. Send only fields you want to change. status and fields must use the dashboard JSON object shapes (not status=1 and not [{type}]).
Permissions
- User must be logged in with a valid bearer token.
- Returned or changed records are limited by the user permissions, team access, folder access, and account settings.
Action
- Updates one entry/tab definition: names, folders, sharing, status map, custom fields, and entry-customer flags.
Push Service
Emits entriessettings.updated.
Automation
No business automation is run for entry settings changes.
Special Instructions
- This updates the tab definition, not rows inside the tab. Use Entries.Update for row data.
- status must be a JSON array/object of statuses. API stores 23-char unique ids, label_en, color_name, and sub_status like dashboard. Sending 1/0 is ignored on update so existing statuses are not wiped.
- fields must be a JSON object keyed by unique ids with input_type. Sending the full object replaces stored fields.
- folders must be a JSON array of folder ids, e.g. ["3"].
- If use_customer_for_entry is changed to 1, entry_customer_folder_id must also be sent.
- After updating, call User.Basic again.
Required Parameters
| Name | Type | Sample | Explanation |
|---|---|---|---|
idpost | int | 745 | Entry/tab id to update. |
Optional Parameters
| Name | Type | Sample | What it gives |
|---|---|---|---|
tab_name_enpost | string | Lead data | English tab name. |
tab_name_hepost | string | Lead data | Hebrew/local tab name. |
folderspost | json | ["3"] | JSON array of folder ids. Alias: folder_name. Do not send a bare id like 12. |
statuspost | json | [{"label_en":"Open","color_name":"#ffa500"}] | Replaces the status map. Send a JSON array or object. API stores dashboard unique ids, label_en, color_name, sub_status. Do not send 1/0; that is ignored on update. |
fieldspost | json | [{"input_type":"text","label_en":"Note","label_he":"Note"}] | Replaces custom fields. Send dashboard unique-id object or a simple array. API stores dashboard shape with 23-char ids, date, input_type, and type-specific keys. |
shard_withpost | json | ["47","51"] | JSON array of team member ids. |
tab_orderpost | int | 10 | Display order for entry tabs when stored. |
iconpost | string | clipboard-list | UI icon name when the table supports it. |
colorpost | string | #2490ef | UI color when the table supports it. |
show_in_headerpost | int | 1 | Show in header. Alias: show_in_dashboard. |
show_in_customerpost | int | 1 | Show this tab on customer screens when stored. |
copy_customer_tabpost | int | 0 | When 1, tab_id_for_cust is required. |
tab_id_for_custpost | int | 8 | Required when copy_customer_tab=1. |
use_customer_for_entrypost | int | 0 | When 1, entry_customer_folder_id is required. |
entry_customer_folder_idpost | int | 12 | Required when use_customer_for_entry=1. |
JSON Structure
status JSON
status is stored like dashboard: object keyed by 23-char unique ids. Sending status replaces the stored map. Sending 1/0 is ignored. sub_status uses sub_stauts_color like dashboard.
{"17845458326a5e02280a638":{"label_en":"Open","color_name":"#ffa500","sub_status":[{"sub_status_label":"Waiting","sub_stauts_color":"#cccccc","sub_status_key":"17845458336a5e02280a639"}]}}fields JSON
fields is stored like dashboard: object keyed by 23-char unique ids. Sending the full object replaces stored fields. Friendly keys like fld_note are converted to unique ids.
{"17845458326a5e02280a638":{"name":"17845458326a5e02280a638","field_no":1,"date":"2026-07-20 11:10:32","input_type":"text","label_en":"Note","label_he":"Note","default_value":""}}folders JSON
folders is a JSON array of folder ids, for example ["3"].
["3"]
Authentication
Send the bearer token returned by Login in the request header.
Authorization: Bearer YOUR TOKEN
Sample Request
{
"url": "\/app\/EntriesSettings.Update",
"method": "POST",
"headers": {
"Authorization": "Bearer YOUR TOKEN"
},
"body": {
"id": "745",
"tab_name_en": "Lead data",
"tab_name_he": "Lead data",
"folders": "[\"3\"]",
"status": "[{\"label_en\":\"Open\",\"color_name\":\"#ffa500\",\"sub_status\":[{\"sub_status_label\":\"Waiting\",\"sub_stauts_color\":\"#cccccc\"}]}]",
"fields": "[{\"input_type\":\"text\",\"label_en\":\"Note\",\"label_he\":\"Note\"}]"
},
"url_user": "https:\/\/{user}.bull36.com\/app\/EntriesSettings.Update",
"url_domain": "https:\/\/{domain}\/app\/EntriesSettings.Update"
}Endpoint
POST /app/EntriesSettings.Update
POST https://{user}.bull36.com/app/EntriesSettings.Update
POST https://{domain}/app/EntriesSettings.UpdateSample Output
{
"success": 1,
"id": 745,
"message": "Record updated successfully.",
"socket_event": "entriessettings.updated"
}JavaScript Example
const token = 'YOUR TOKEN';
const body = new URLSearchParams({
id: '745',
tab_name_he: 'Lead data',
folders: JSON.stringify(['3']),
status: JSON.stringify([
{
label_en: 'Open',
color_name: '#ffa500',
sub_status: [{ sub_status_label: 'Waiting', sub_stauts_color: '#cccccc' }]
}
]),
fields: JSON.stringify([
{ input_type: 'text', label_en: 'Note', label_he: 'Note' }
])
});
const res = await fetch('/app/EntriesSettings.Update', {
method: 'POST',
headers: { Authorization: `Bearer ${token}` },
body
});
console.log(await res.json());Error Example
{
"success": 0,
"message": "Record was not found."
}