getTransactions
https://triport.io/rpc/tonReturns an account's transactions newest-first with paired cursor pagination.
getTransactions returns transactions for one TON account in newest-first
order. Each transaction has a required transaction ID; the schema also permits
serialized data, fee, Unix time, inbound message, and outbound messages.
Pagination uses a pair, not an independent scalar cursor. To continue, take
both lt and hash from the oldest transaction returned and send them together
in the next request. to_lt supplies an optional lower logical-time boundary.
The archival flag is a routing hint for a measured deep-history server. It is
not a promise of continuous history and does not change an unavailable old
range into an empty successful response.
Parameters
JSON-RPC params is a by-name object.
Params: object (by-name).
addressstringrequiredlimitintegeroptional1, default 10.ltstringoptionalhashstringoptionallt for continuation.to_ltstringoptionalarchivalbooleanoptionalfalse.Response
Response fields
| Field | Type | Description |
|---|---|---|
jsonrpc | string | JSON-RPC protocol version. |
id | number or string | Correlates the response with the request. |
result | array | Transactions in newest-first order. |
result[].transaction_id | object | Required transaction cursor pair. |
result[].transaction_id.lt | string | Transaction logical time as unsigned decimal text. |
result[].transaction_id.hash | string | Transaction hash. |
result[].data | string | Optional serialized transaction data. |
result[].fee | string | Optional fee value encoded as text. |
result[].utime | integer | Optional Unix timestamp. |
result[].in_msg | object | Optional inbound-message object. |
result[].out_msgs | array | Optional outbound-message objects. |
The JSON is copied from the accepted live fixture.
The fixture sanitizer replaces transaction BoC data, so the displayed data
value documents representation rather than a reusable transaction payload.
Errors
See TON errors for the shared envelope and retention handling.
| Code | Meaning | When it happens |
|---|---|---|
-32602 | Invalid params | The address, limit, cursor pair, boundary, or named-object structure is invalid. |
beyond_retention | History unavailable | The requested cursor falls outside the selected liteserver's history window. |
-32601 | Method not found | The method is outside the published read-only catalog. |
401 | Unauthorized | The API key is missing or invalid. |
429 | Rate limited | The ton_read_rpc_heavy budget is exceeded. |
Examples
const params = { address: "EQCxE6mUtQJKFnGfaROTKOt1lZbDiiX1kCixRv7Nw2Id_sDs", limit: 1 };
const response = await fetch("https://triport.io/rpc/ton", {
method: "POST",
headers: { "x-token": process.env.TRIPORT_API_KEY, "Content-Type": "application/json" },
body: JSON.stringify({ jsonrpc: "2.0", id: "transactions", method: "getTransactions", params }),
});
const { result: transactions } = await response.json();
const next = transactions.at(-1)?.transaction_id;Notes
- Preserve both values from
transaction_idfor pagination;ltorhashalone is not a cursor. - Pruned liteservers had a measured floor of 86 860 000. Two nodes answered
from genesis, but
ls-17had a measured continuity gap. archival: trueis best-effort routing. No REST gateway, transaction stream, write method, or WebSocket subscription is published for TON.- Named params and response matching by
idapply to batch calls. - Related method:
getAddressInformation.