POST
Files.Edit
Update one customer file display name/folder. The route checks customer access, runs files.updated automation, and emits realtime files.updated.
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 Files record after validating permissions and input fields.
Push Service
Pushes event files.updated to users who should see this change.
Automation
Runs automation event files.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 |
|---|---|---|---|
customer_idpost | int | 123 | Customer id that owns the file. |
file_idpost | int | 456 | File id. You may also send id. |
Optional Parameters
| Name | Type | Sample | What it gives |
|---|---|---|---|
file_namepost | string | Signed contract | User-facing display name when editing a file. |
folderpost | string | contracts | File folder/type when editing a file. |
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\/Files.Edit",
"method": "POST",
"headers": {
"Authorization": "Bearer YOUR TOKEN"
},
"body": {
"customer_id": "123",
"file_id": "456",
"file_name": "Signed contract"
},
"url_user": "https:\/\/{user}.bull36.com\/app\/Files.Edit",
"url_domain": "https:\/\/{domain}\/app\/Files.Edit"
}Endpoint
POST /app/Files.Edit
POST https://{user}.bull36.com/app/Files.Edit
POST https://{domain}/app/Files.EditSample Output
{
"success": 1,
"message": "File updated",
"file_id": "456",
"customer_id": "123",
"automation_event": "files.updated",
"socket_event": "files.updated"
}JavaScript Example
const token = 'YOUR TOKEN';
const body = new URLSearchParams();
body.set('customer_id', '123');
body.set('file_id', '456');
body.set('file_name', 'Signed contract');
const res = await fetch('/app/Files.Edit', { method: 'POST', headers: { Authorization: 'Bearer ' + token }, body });
const data = await res.json();
console.log(data);Error Example
{
"success": 0,
"message": "Missing required parameter: customer_id, file_id"
}