Write to the support team
Add a message to a request you opened. Whatever its status, including solved, the request goes back to to_handle.
Files are sent as multipart form data, in a field called files that is repeated once per file. At most 5 files, each at most 10 MB, of the types jpg, jpeg, png, gif, webp, heic, pdf, txt and log. A file that breaks any of these answers 422 on files or on files.0, files.1 and so on, and nothing is kept.
Parameters
Sent as JSON. Anything not listed here is ignored.
The id of the request. One belonging to another account answers 404.
What you want to say, up to 20,000 characters. A body left empty answers 422.
Files to send with the message. Repeat the field once per file, up to 5.
Returns
The message object that was written. A request of another account answers 404.
The message.
Always support_message.
The id of the message.
Everything the message holds.
message when the person who asked wrote it, reply when the support team did. An internal note is never shown here.
The name of the person who wrote it.
Whether the support team wrote it.
What was written, as plain text.
The files sent with it. An empty list when there are none.
One file.
The id of the file, which the download address takes.
The name the file had when it was sent.
The type of the file, such as image/png.
How large the file is, in bytes.
When it was written, as a count of seconds since 1970.
Rate limit
Sixty requests per minute, per user, shared by every key and device. Every answer carries the budget left in X-RateLimit-Remaining.
Keys act as you, with exactly the access you have. Make one per integration so you can revoke it alone.