List support requests
List the support requests of your account, the most recently active first. The messages are left out of a list. Read one request to get its thread.
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.
Keep only the requests in this status: to_handle, waiting_on_user or solved. Any other value answers 422 on status.
Which page to answer with.
How many records one page holds, between 1 and 100. A number outside the range is brought back into it rather than refused.
Returns
A page of support request objects, and how many there are in all. Only the requests of your account are listed.
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 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.
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.
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.