Pagination
All list endpoints in the API use a standard cursor-based pagination pattern.
Request Parameters
| Parameter | Type | Default | Validation | Description |
|---|---|---|---|---|
page | integer | 1 | min: 1 | Page number to retrieve |
limit | integer | 10 | min: 1, max: 100 | Number of items per page |
Parameters are passed as query strings:
GET /v1/accounts?page=2&limit=25
Response Format
All paginated responses share this structure:
{
"data": [...],
"page": 2,
"per_page": 25,
"total": 148
}
| Field | Type | Description |
|---|---|---|
data | array | Array of resource objects for the current page |
page | integer | Current page number |
per_page | integer | Number of items per page |
total | integer | Total number of items across all pages |
Calculating Total Pages
total_pages = ceil(total / per_page)
Example
Request:
curl "https://integration.test-custody.tokenizationtr.com/v1/accounts?page=1&limit=2" \
-H "Authorization: Bearer <token>" \
-H "X-Target-Server: accounts"
Response:
{
"data": [
{
"id": "550e8400-e29b-41d4-a716-446655440000",
"name": "Main Account",
"node_id": "660e8400-e29b-41d4-a716-446655440000",
"type": "organisation",
"status": 1,
"created_at": "2025-01-01T00:00:00Z",
"updated_at": "2025-01-01T00:00:00Z",
"deleted_at": null
},
{
"id": "550e8400-e29b-41d4-a716-446655440001",
"name": "Customer Account",
"node_id": "660e8400-e29b-41d4-a716-446655440000",
"type": "customer-segregated",
"status": 1,
"created_at": "2025-01-02T00:00:00Z",
"updated_at": "2025-01-02T00:00:00Z",
"deleted_at": null
}
],
"page": 1,
"per_page": 2,
"total": 15
}
note
If page or limit are omitted, the defaults of page=1 and limit=10 are used.