POST
Support.Add
Create a SUPPORT request through the existing support workflow, including its initial conversation and configured notifications. Text only. Uses the signed-in organization unless support staff select another organization.
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
- Creates a Support record or sends the requested data after validation.
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.
- 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 |
|---|---|---|---|
subjectpost | string | Login problem | Ticket subject, 1 to 255 UTF-8 bytes. |
notespost | string | Cannot sign in | Original ticket description, up to 20000 bytes. Use Reply or InternalReply to append conversation messages. |
Optional Parameters
| Name | Type | Sample | What it gives |
|---|---|---|---|
due_datepost | date | 2026-11-15 | Due date, YYYY-MM-DD. 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. |
ratingpost | int | 3 | Urgency, 1 to 5. |
member_idpost | int | 47 | Support staff only: assign to a support team member, or 0 to unassign. |
sub_titlepost | string | Investigating | Support staff only: secondary/internal ticket title. |
customer_owner_idpost | int | 123 | Support staff only: create for this organization owner id; defaults to the signed-in organization. |
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\/Support.Add",
"method": "POST",
"headers": {
"Authorization": "Bearer YOUR TOKEN",
"Content-Type": "application\/json"
},
"body": {
"subject": "Login problem",
"notes": "Cannot sign in"
},
"url_user": "https:\/\/{user}.bull36.com\/app\/Support.Add",
"url_domain": "https:\/\/{domain}\/app\/Support.Add"
}Endpoint
POST /app/Support.Add
POST https://{user}.bull36.com/app/Support.Add
POST https://{domain}/app/Support.AddSample Output
{
"success": 1,
"ticket_id": 123
}JavaScript Example
const token = 'YOUR TOKEN';
const body = {
"subject": "Login problem",
"notes": "Cannot sign in"
};
const res = await fetch('/app/Support.Add', {
method: 'POST',
headers: { Authorization: `Bearer ${token}`, 'Content-Type': 'application/json' },
body: JSON.stringify(body)
});
const data = await res.json();
console.log(data);Error Example
{
"success": "0",
"error": "bearer_token_required",
"message": "Authorization bearer token is required. Send header: Authorization: Bearer YOUR TOKEN"
}