Ticket.Add

Permissions

• User must be logged in with a valid bearer token.
• Returned or changed records are limited by the user permissions, team access, folder access, and account settings.

Action

• Creates a Ticket record or sends the requested data after validation.

Push Service

Pushes event ticket.created to users who should see this change.

Automation

Runs automation event ticket.created with the record id and submitted parameters after the action succeeds.

Special Instructions

• Ticket custom fields are NOT the English/Hebrew label. In Tickets settings each field is stored with name = a-{unix timestamp}, e.g. a-1731562297. The dashboard form posts that id (checkbox/multi-select: a-1731562778[]).
• Keys like a-YES_NO_EN or a-SELECT_EN do not match the form and are rejected. Look up ids in Settings → Tickets custom fields (field name column) or from a dashboard new_ticket payload.
• Send either top-level POST keys ([email protected]) or custom_fields JSON {"a-1731562297":"[email protected]"}. Stored JSON keys never include [].
• Validation matches the dashboard form: email fields must be a valid email, number fields must be numeric, select/radio/checkbox values must be an option_value from settings, and a required field that is sent empty is rejected. Topic+messages without custom fields still works (same as API before).
• With customer_id/cust_id: phone, email, name, address, ticket_name are optional (dashboard auto-fills from contactus). Do NOT send phone=-- or other dash-only placeholders; omit phone or leave it empty so auto-fill runs. A real phone number is fine when you want to override.
• ticket_name is the dashboard TICKET NAME column (separate from customer_name). When cust_id is sent and ticket_name is omitted, it is filled from the customer name (same as picking a customer in the create form).
• Sets last_status_time and last_assign_time to open_date (ticket automation timers for in_status / not_assigned rules).
• owner_id is set automatically to the organization owner (user_detail.id / JWT owner_id), same as dashboard Tickets::new_ticket ($Org[id]). Do not send owner_id in the body — it is ignored. Response includes owner_id for verification.
• Dates: Y-m-d H:i:s. Bearer token required.

Required Parameters

Optional Parameters

Authentication

Send the bearer token returned by Login in the request header.

Authorization: Bearer YOUR TOKEN

Sample Request

{
    "url": "\/app\/Ticket.Add",
    "method": "POST",
    "headers": {
        "Authorization": "Bearer YOUR TOKEN"
    },
    "body": {
        "topic": "Payment issue",
        "messages": "Customer needs help.",
        "cust_id": "123",
        "ticket_name": "John Demo",
        "ticket_department": "2",
        "assign_member_id[]": [
            "211",
            "212"
        ],
        "due_date": "2026-07-20 09:00:00",
        "from_time_ticket": "09:00",
        "to_time_ticket": "11:00",
        "rating": "3",
        "a-1731562297": "[email protected]",
        "a-1731562578": "10",
        "a-1731562778[]": "2"
    },
    "curl_multipart": "curl --location 'https:\/\/YOUR_HOST\/app\/Ticket.Add' \\\n--header 'Authorization: Bearer YOUR_TOKEN' \\\n--form 'topic=Payment issue' \\\n--form 'messages=Customer needs help.' \\\n--form 'cust_id=123' \\\n--form 'due_date=2026-07-20 09:00:00' \\\n--form 'assign_member_id[]=211' \\\n--form 'assign_member_id[]=212' \\\n--form 'image_upload=@\/path\/to\/file.png'",
    "url_user": "https:\/\/{user}.bull36.com\/app\/Ticket.Add",
    "url_domain": "https:\/\/{domain}\/app\/Ticket.Add"
}

Endpoint

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

Sample Output

{
    "success": 1,
    "output": "1",
    "message": "Success",
    "insert_id": 900,
    "ticket_id": 900,
    "owner_id": 14,
    "u_id": 14,
    "cust_id": 123,
    "customer_name": "John Demo",
    "ticket_name": "John Demo",
    "assign_member_id": [
        "211",
        "212"
    ],
    "files": [],
    "automation_event": "ticket.created",
    "socket_event": "ticket.created"
}

JavaScript Example

const token = 'YOUR TOKEN';

// Custom field keys must be a-{numeric_id} from Tickets settings (same as dashboard new_ticket), not labels.
const body = new URLSearchParams({
  topic: 'Payment issue',
  messages: 'Customer needs help.',
  cust_id: '123',
  ticket_department: '2',
  assign_member_id: '211,212',
  due_date: '2026-07-20 09:00:00',
  'a-1731562297': '[email protected]'
});

const res = await fetch('/app/Ticket.Add', {
  method: 'POST',
  headers: { Authorization: 'Bearer ' + token },
  body
});

const data = await res.json();
console.log(data.ticket_id, data.assign_member_id); // ["211","212"]

// With file (multipart) — repeat assign_member_id[]
const form = new FormData();
form.append('topic', 'Payment issue');
form.append('messages', 'Customer needs help.');
form.append('cust_id', '123');
form.append('due_date', '2026-07-20 09:00:00');
form.append('assign_member_id[]', '211');
form.append('assign_member_id[]', '212');
form.append('a-1731562297', '[email protected]');
form.append('image_upload', fileInput.files[0]);

const res2 = await fetch('/app/Ticket.Add', {
  method: 'POST',
  headers: { Authorization: 'Bearer ' + token },
  body: form
});

Error Example

{
    "missing": {
        "success": 0,
        "message": "Missing required parameter: topic, messages"
    },
    "request_blocked_example": {
        "success": "0",
        "error": "request_blocked",
        "message": "Request blocked by security rules",
        "reasons": [
            {
                "type": "sql_comment_injection",
                "field": "body.phone"
            }
        ],
        "note": "Usually caused by phone=--. Omit phone or send a real number \/ empty value when using customer_id."
    }
}