POST

Ticket.CompletionReasonAdd

Create an all_status row with type=ticket_completion_reason (dashboard Settings → Completion Reasons → Add). Requires manager permission. Enable the feature first with Ticket.SettingsUpdate ticket_completion_reason_settings=1.

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 Ticket.CompletionReasonAdd 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

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.
Requires manager permission.
At least one of name_en or name_he is required. If one is empty, it is copied from the other.
Aliases: en → name_en, he → name_he.
Use Ticket.CompletionReasonList to fill the close-ticket reason dropdown.

Required Parameters

No body parameters are required for this function.

Optional Parameters

Name	Type	Sample	What it gives
`name_en` post	string	`Resolved`	English label. Alias: en. Required if name_he is empty.
`name_he` post	string	`נפתר`	Hebrew label. Alias: he. Required if name_en is empty.
`color` post	string	`#64748b`	Display color (default #64748b).

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\/Ticket.CompletionReasonAdd",
    "method": "POST",
    "headers": {
        "Authorization": "Bearer YOUR TOKEN"
    },
    "body": {
        "name_en": "Resolved",
        "name_he": "נפתר",
        "color": "#64748b"
    },
    "url_user": "https:\/\/{user}.bull36.com\/app\/Ticket.CompletionReasonAdd",
    "url_domain": "https:\/\/{domain}\/app\/Ticket.CompletionReasonAdd"
}

Endpoint

POST /app/Ticket.CompletionReasonAdd
POST https://{user}.bull36.com/app/Ticket.CompletionReasonAdd
POST https://{domain}/app/Ticket.CompletionReasonAdd

Sample Output

{
    "success": 1,
    "message": "Success",
    "id": 10,
    "data": {
        "id": 10,
        "en": "Resolved",
        "he": "נפתר",
        "name_en": "Resolved",
        "name_he": "נפתר"
    }
}

JavaScript Example

const token = 'YOUR TOKEN';
const body = new URLSearchParams({ name_en: 'Resolved', name_he: 'Resolved', color: '#64748b' });
const res = await fetch('/app/Ticket.CompletionReasonAdd', { method: 'POST', headers: { Authorization: 'Bearer ' + token }, body });
console.log(await res.json());

Error Example

{
    "success": 0,
    "message": "Missing required parameter: name_en or name_he"
}