Entries Settings
Entries Settings routes manage the tab definitions themselves (names, folders, status map, custom fields). They do not add rows inside a tab. Use Entries.* for row data after the tab exists.
Required Names
- EntriesSettings.Add requires both tab_name_en and tab_name_he, same as the dashboard create modal.
- tab_name_he is not optional on create.
JSON Columns
- status is a JSON object of status rows keyed by unique ids, with label_en, color_name, and sub_status. It is not int 1/0 and is not active/inactive. Friendly keys like st_open are converted to 23-char dashboard ids.
- fields is a JSON object keyed by unique field ids. Each field uses input_type (not type), field_no, label_en, and label_he.
- folders is a JSON array of folder ids, for example ["3"]. Do not send a bare id like 12.
- shard_with is a JSON array of team member ids, for example ["47","51"].
After Save
- Call User.Basic again so the UI has the new or updated entry id, names, and field definitions.
- Use the returned id as entry_id on Entries.List/Add/Get/Update/Delete.
Common Flow
- Call User.Basic to see existing tabs.
- Create a tab with EntriesSettings.Add using tab_name_en, tab_name_he, and dashboard JSON for status/fields/folders.
- Update or delete the tab definition with EntriesSettings.Update/Delete.
- Add rows inside the tab with Entries.Add using the created id as entry_id.