List support requests of the instance
List the support requests of every account, the oldest first, 50 to a page. The thread, the account facts and the status changes are left out of a list. Read one request to get them.
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.
This endpoint also answers QUERY, with the same parameters sent in the request body. How QUERY works.
Query parameters
Sent as JSON. Anything not listed here is ignored.
Which requests to list: to_handle, waiting_on_user, solved or all. Any other value is taken as to_handle.
Keep only the requests that mention this text.
Keep only one category: feature, billing, email, question or technical.
Keep only the requests of the user with this id.
Keep only the requests of one age: day for under 24 hours, week for 1 to 7 days, old for older than 7 days.
Which page to answer with.
Returns
A page of support request objects, how many there are in all, and in meta.counts how many each view holds.
The support requests on this page. An empty list rather than an error when there are none.
One 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.
Where you are in the collection.
The page this is, counting from 1.
How many one page holds, which is the size that was asked for once it has been brought into the allowed range.
How many support requests there are in all, not how many are on this page.
How many requests each view holds under the filters you sent, apart from the view itself.
Requests waiting for an answer.
Requests answered and waiting on the person.
Requests marked as solved.
Every request.
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.