Mark a support request as solved
Tell the support team the request needs nothing more. Its status becomes solved. Writing to it again reopens it.
A request that is already solved answers 422 on status with the message This request is already solved.
Path parameters
Sent as JSON. Anything not listed here is ignored.
The id of the request. One belonging to another account answers 404.
Returns
The support request object as it stands now, without its messages. A request of another account answers 404.
The support request.
Always support_request. It names the kind of record, so a caller holding several kinds can tell them apart without looking at where they came from.
The id of this record, as a string even when it reads as a number. It is what every endpoint naming this record takes.
Everything the record holds.
The reference to quote when writing to the support team, such as MON-482913.
What the request is about: feature, billing, email, question or technical.
The title the request was opened with.
Where the request stands: to_handle when the support team has yet to answer, waiting_on_user when it has and awaits you, or solved.
The status as the application words it for the person who asked, in the language of the account.
When the request was opened, as a count of seconds since 1970.
When anybody last wrote in it, the person who asked or the support team, as a count of seconds since 1970. A change of status alone does not move it.
When it was marked as solved, as a count of seconds since 1970, or null while it is open.
Where to find this record.
The absolute address this record is read from.
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.