POST

Chat.MissionMessages

Return internal messages linked to one mission customer.

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 Chat.MissionMessages function and returns JSON.

Push Service

No push is sent because this function only reads data or returns helper information.

Automation

No automation is run for this function.

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
`mission_id` post	int	`500`	Mission id.

Optional Parameters

Name	Type	Sample	What it gives
`project_id` post	int	`700`	Project id when the mission belongs to a project.
`limit` post	int	`25`	Optional caller-side max. Values above 25 are capped before forwarding.
`sort` post	string	`time_asc`	Optional caller-side sort hint for consumers of the returned data.

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\/Chat.MissionMessages",
    "method": "POST",
    "headers": {
        "Authorization": "Bearer YOUR TOKEN"
    },
    "body": {
        "mission_id": "500"
    },
    "url_user": "https:\/\/{user}.bull36.com\/app\/Chat.MissionMessages",
    "url_domain": "https:\/\/{domain}\/app\/Chat.MissionMessages"
}

Endpoint

POST /app/Chat.MissionMessages
POST https://{user}.bull36.com/app/Chat.MissionMessages
POST https://{domain}/app/Chat.MissionMessages

Sample Output

{
    "success": 1,
    "mission_id": 500,
    "customer_id": 123,
    "data": [
        {
            "id": 3283714,
            "message": "Mission note text"
        }
    ]
}

Count Only

Use the matching count route with the same filters when the UI only needs total rows for paging.

{
    "url": "\/app\/Chat.MissionMessages",
    "url_user": "https:\/\/{user}.bull36.com\/app\/Chat.MissionMessages",
    "url_domain": "https:\/\/{domain}\/app\/Chat.MissionMessages",
    "method": "POST",
    "headers": {
        "Authorization": "Bearer YOUR TOKEN"
    },
    "body": {
        "mission_id": "500"
    },
    "sample_output": {
        "success": 1,
        "count": 123
    },
    "notes": {
        "data_count": "Use count(data) for returned mission chat messages.",
        "max_limit": 25
    }
}

Count JavaScript

const token = 'YOUR TOKEN';
const body = new URLSearchParams();
body.set('mission_id', '500');

const res = await fetch('https://{domain}/app/Chat.MissionMessages', {
  method: 'POST',
  headers: { Authorization: `Bearer ${token}` },
  body
});
const data = await res.json();
console.log(data.count);

JavaScript Example

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

Error Example

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