Change the status of a support request
Move a request to another status without writing to the person.
Only an administrator of this instance can use these endpoints, and only with an API key that carries the administration scope by name. Anybody else, including an administrator whose key does not carry it, gets 404 as though the endpoint did not exist.
Parameters
Sent as JSON. Anything not listed here is ignored.
The id of the request, of any account on the instance.
The status to move to: to_handle, waiting_on_user or solved. Any other value answers 422 on status.
Returns
The support request object as it stands now, without its messages and its status changes. Read the request to get them.
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 the person quotes when writing to the support team, such as MON-482913.
The account the request was opened from.
Who asked.
The name of the person who opened the request, or null once their user is deleted.
Where replies are emailed, or null once their user is deleted.
What the request is about: feature, billing, email, question or technical.
The title the request was opened with.
to_handle when the person is waiting for an answer, waiting_on_user when the team is, or solved.
The status as the administrators read it, in the language of the signed in administrator.
The version of the application the request was opened from.
The language the person was using when they opened it.
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.