Support.Reply
Append a customer-visible reply with optional attachment to a SUPPORT request. Support replies use configured customer email/WhatsApp notifications and realtime updates; customer replies reopen the request. Do not blindly retry after a timeout because replies are appended. Send message and/or one multipart file; file-only replies are supported. Allowed files are validated by content and extension, up to 25 MiB. Verify the saved attachment with Messages.media_url.
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 Support record after validating permissions and input fields.
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 |
|---|---|---|---|
ticket_idpost | int | 123 | Support ticket id. Access is restricted to the signed-in organization or support staff. |
Optional Parameters
| Name | Type | Sample | What it gives |
|---|---|---|---|
messagepost | string | We are checking this issue. | Plain text, up to 20000 UTF-8 bytes. Required when file is absent. Visible to the customer. |
filefile | file | report.pdf | One nonempty multipart binary attachment, maximum 25 MiB (26214400 bytes). Required when message is absent. Allowed extensions: pdf, txt, csv, doc, docx, xls, xlsx, ppt, pptx, odt, ods, odp, jpg, jpeg, png, gif, tif, tiff, zip, rar, mp3, wav, ogg, mp4, webm. Detected content must match the extension. File arrays, URLs and executable/HTML content are rejected. Messages returns the stored media_url. Internal attachments are visible only in the staff thread; existing file-host access rules apply. |
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.Reply",
"method": "POST",
"headers": {
"Authorization": "Bearer YOUR TOKEN"
},
"body": {
"ticket_id": "123",
"message": "We are checking this issue.",
"file": "(binary file: report.pdf)"
},
"url_user": "https:\/\/{user}.bull36.com\/app\/Support.Reply",
"url_domain": "https:\/\/{domain}\/app\/Support.Reply"
}Endpoint
POST /app/Support.Reply
POST https://{user}.bull36.com/app/Support.Reply
POST https://{domain}/app/Support.ReplySample Output
{
"success": 1,
"ticket_id": 123
}JavaScript Example
// Use a file input or a File/Blob; omit file for text-only replies.
const body = new FormData();
body.append('ticket_id', '123');
body.append('message', 'Please find the report attached.');
body.append('file', fileInput.files[0]);
const res = await fetch('/app/Support.Reply', {
method: 'POST',
headers: { Authorization: `Bearer ${token}` },
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"
}