GET
/v1/ticketsList tickets
The account's support tickets.
API v1 · Updated 2026-10-21View .md
Call it through the gateway https://api.tino.vn/v1 with a token that has the tickets:read scope; see Calling the Tino API.
Authentication
Send the token in the header Authorization:
Authorization: Bearer <token>
Tokens that can call it: app tokens (tinoat_, Sign in with Tino) or personal API tokens (tinopat_).
Scopes
tickets:readView support tickets
Parameters
Query
| Name | Type | Required | Description |
|---|---|---|---|
page | integer | Optional | Zero-based page index. page=0 is the first page; the response echoes it 1-based in page.current. Default: `0`. |
perpage | integer | Optional | Rows per page. Defaults to the account's RecordsPerPage setting. |
orderby | string | Optional | Sort expression in the form `field|DESC` or `field|ASC`, e.g. `date|DESC`. |
filter | object | Optional | Endpoint-specific filters, serialised as filter[key]=value. |
Response
The route's JSON answer, in the same shape as UserAPI returns it (Personal data). Live sample from a test account with personal data masked; long arrays and strings are trimmed (… N more item(s), … N more line(s)).
Error codes
| Error code | Description |
|---|---|
401 · invalid_token | The token is wrong, expired or revoked. |
403 · insufficient_scope | The token lacks the tickets:read scope. |
403 · ip_not_allowed | A personal API token called from an IP outside its allow-list. |
Business errors of a route usually come as HTTP 200 with {"error": ["<code>"]}; see common error codes.