POST

FileFolders.Edit

Update a customer file folder. The route validates folder id and allowed fields, runs filefolders.edit.updated automation, and emits realtime filefolders.edit.updated so file folder pickers can refresh.

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

Updates the requested FileFolders record after validating permissions and input fields.

Push Service

Pushes event filefolders.edit.updated to users who should see this change.

Automation

Runs automation event filefolders.edit.updated with the record id and submitted parameters after the action succeeds.

Special Instructions

Send the bearer token on protected calls with Authorization: Bearer YOUR TOKEN.
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.
Send parameters as POST body fields exactly as documented.
Send date/time values in UTC Y-m-d H:i:s format when a date or datetime field is used.

Required Parameters

Name	Type	Sample	Explanation
`folder_id` post	int	`12`	Folder id to update. You may also send files_of_customer_id.
`name_he` post	string	`חוזים`	Updated Hebrew folder name.

Optional Parameters

Name	Type	Sample	What it gives
`name_en` post	string	`Contracts`	Updated English folder name.
`sub_files_of_customer_id` post	array\|string	`44`	Existing sub-folder ids to update.
`sub_name_en` post	array\|string	`Signed`	English sub-folder names to add or update.
`sub_name_he` post	array\|string	`חתום`	Hebrew sub-folder names to add or update.

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\/FileFolders.Edit",
    "method": "POST",
    "body": {
        "folder_id": "12",
        "name_en": "Contracts",
        "name_he": "חוזים"
    },
    "headers": {
        "Authorization": "Bearer YOUR TOKEN"
    },
    "url_user": "https:\/\/{user}.bull36.com\/app\/FileFolders.Edit",
    "url_domain": "https:\/\/{domain}\/app\/FileFolders.Edit"
}

Endpoint

POST /app/FileFolders.Edit
POST https://{user}.bull36.com/app/FileFolders.Edit
POST https://{domain}/app/FileFolders.Edit

Sample Output

{
    "success": 1,
    "message": "FileFolders.Edit updated",
    "id": "12",
    "automation_event": "filefolders.edit.updated",
    "socket_event": "filefolders.edit.updated"
}

JavaScript Example

const token = 'YOUR TOKEN';
const body = new URLSearchParams({ folder_id: '12', name_he: 'Contracts', name_en: 'Contracts' });
const res = await fetch('/app/FileFolders.Edit', { method: 'POST', headers: { Authorization: 'Bearer ' + token }, body });
const data = await res.json();
console.log(data);

Error Example

{
    "success": 0,
    "message": "Failed"
}