/service/@id/tinopay/transactionsTransaction history
Newest first, with fields named like the webhook payload (transactionDate in ISO 8601). Filters: bank_account_id, virtual_account (exact VA number), type (in, out), from, to (Y-m-d, by transaction date), q (description, transaction code, VA number, reference code), webhook_status (none not sent, failed, success); paginated, per_page up to 100.
A TinoPay service route: call it with the service owner's sign-in token; the /v1 gateway (app tokens, personal tokens) does not expose TinoPay yet. See Getting started with TinoPay.
Authentication
Send the token in the header Authorization:
Authorization: Bearer <token>
Tokens that can call it: the TinoPay service owner's sign-in token (the tino.vn client area token).
Parameters
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
id | int | Required | TinoPay service ID |
Query
| Name | Type | Required | Description |
|---|---|---|---|
bank_account_id | string | — | — |
virtual_account | string | — | Số VA chính xác |
type | string | — | in | out |
from | string | — | Y-m-d |
to | string | — | Y-m-d |
q | string | — | Nội dung, mã giao dịch, số VA, mã tham chiếu |
webhook_status | string | — | none | failed | success |
page | int | — | — |
per_page | int | — | ≤ 100 |
Response
Sample built from the TinoPay API v1 documentation (Tino relays TinoPay data as is); values are examples.
Error codes
| Error code | Description |
|---|---|
404 · service_not_found, invalid method | The service does not belong to the signed-in account, or is not TinoPay. |
403 · service_not_active | The service is neither Active nor Suspended. |
403 · MERCHANT_SUSPENDED | The merchant is suspended: writes are blocked, GET still works. |
404 · RESOURCE_NOT_FOUND | The resource does not exist or does not belong to the merchant. |
422 · VALIDATION_FAILED | Invalid data; details lists the fields. |
502 · NETWORK_ERROR…, 504 | The connection between Tino and the partner is interrupted (504: HTML body, request took too long): a Tino-side error, not a token problem. Keep the token, retry later. |
Errors look like {"error": ["<CODE>"], "message", "details", "request_id"}; every code is in Getting started with TinoPay.