POST

Recordings.UpdateNote

Update the note saved on one call recording. The user id is taken from the bearer token, not from client input. The route checks customer/recording permission, runs automation, and sends a realtime update.

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

Runs the Recordings.UpdateNote function and returns JSON.

Push Service

Pushes event recordings.updated to users who should see this change.

Automation

Runs automation event recordings.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.

Required Parameters

Name	Type	Sample	Explanation
`recording_id` post	int	`600`	Recording id to update. id or data_id are also accepted.
`note` post	longtext	`Customer asked to call again tomorrow.`	New note text. Quotes and JSON characters are safe because the route uses parameterized SQL.

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\/Recordings.UpdateNote",
    "method": "POST",
    "headers": {
        "Authorization": "Bearer YOUR TOKEN"
    },
    "body": {
        "recording_id": "600",
        "note": "Customer asked to call again tomorrow."
    },
    "url_user": "https:\/\/{user}.bull36.com\/app\/Recordings.UpdateNote",
    "url_domain": "https:\/\/{domain}\/app\/Recordings.UpdateNote"
}

Endpoint

POST /app/Recordings.UpdateNote
POST https://{user}.bull36.com/app/Recordings.UpdateNote
POST https://{domain}/app/Recordings.UpdateNote

Sample Output

{
    "success": 1,
    "message": "Recording note updated.",
    "recording_id": 600,
    "customer_id": 123,
    "automation_event": "recordings.updated",
    "socket_event": "recordings.updated"
}

JavaScript Example

const token = 'YOUR TOKEN';
const body = new URLSearchParams({ recording_id: '600', note: 'Customer asked to call again tomorrow.' });
const res = await fetch('/app/Recordings.UpdateNote', { method: 'POST', headers: { Authorization: `Bearer ${token}` }, body });
const data = await res.json();
console.log(data);

Error Example

{
    "success": "0",
    "message": "Missing required parameter: recording_id"
}