POST

Meeting.Edit

Update an existing customer meeting. This is for customer combo meetings, not doctor appointments.updated automation, and sends realtime meeting.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 Meeting record after validating permissions and input fields.

Push Service

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

Automation

Runs automation event meeting.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
`meeting_id` post	int	`300`	Meeting id. You may also send combo_id.
`cust_id` post	int	`123`	Main customer id.
`second_cust_id` post	int	`124`	Second customer id for the meeting.
`date` post	date	`2026-07-20`	Meeting date in YYYY-MM-DD format. Send date filters and date values as UTC Y-m-d H:i:s when the route accepts date/time; date-only table columns store the Y-m-d date part.
`start_time` post	time	`10:00`	Meeting start time. Send time values as H:i:s. If the route also has a date field, send that date as UTC Y-m-d H:i:s.
`duration` post	int	`30`	Duration in minutes.

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\/Meeting.Edit",
    "method": "POST",
    "headers": {
        "Authorization": "Bearer YOUR TOKEN"
    },
    "body": {
        "meeting_id": "300",
        "cust_id": "123",
        "second_cust_id": "124",
        "date": "2026-07-20",
        "start_time": "10:00",
        "duration": "30"
    },
    "url_user": "https:\/\/{user}.bull36.com\/app\/Meeting.Edit",
    "url_domain": "https:\/\/{domain}\/app\/Meeting.Edit"
}

Endpoint

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

Sample Output

{
    "success": 1,
    "message": "Combo meeting update Successfully",
    "meeting_id": "300",
    "automation_event": "meeting.updated",
    "socket_event": "meeting.updated"
}

JavaScript Example

const token = 'YOUR TOKEN';
const body = new URLSearchParams({});
// Fill body fields from the Sample Request JSON above.
const res = await fetch('/app/Meeting.Edit', { method: 'POST', headers: { Authorization: 'Bearer ' + token }, body });
const data = await res.json();
console.log(data);

Error Example

{
    "success": 0,
    "message": "Combo meeting update Failed"
}