Pagination & Filtering
Standard limit/page pagination, time_range and from/to filters, and sort_by/sort_order parameters shared across most Trasys Public API list endpoints.
When retrieving collections of resources, the API provides standard parameters to help you paginate through large datasets and filter results by time range.
Pagination Parameters
Most endpoints that return multiple items support standard limit and offset-based pagination.
| Parameter | Type | Default | Description |
|---|---|---|---|
limit | integer | 50 | The number of items to return per page. The maximum allowed limit is typically 100. |
page | integer | 1 | The page number to retrieve, starting at 1. |
Response Format
Endpoints supporting pagination will return a meta object alongside the data array:
{
"data": [
// ... items ...
],
"meta": {
"page": 1,
"limit": 50,
"total": 1240,
"hasMore": true
}
}Time Range Filters
Endpoints that query time-series data (like logs, traces, and metrics) commonly support time range filtering.
| Parameter | Type | Example | Description |
|---|---|---|---|
time_range | string | 24h | A shorthand string for recent time ranges. Supported values: 1h, 24h, 7d, 30d. |
from | string | 2026-06-01T00:00:00Z | Absolute ISO 8601 timestamp for the start of the range. |
to | string | 2026-06-01T23:59:59Z | Absolute ISO 8601 timestamp for the end of the range. |
If you provide time_range, it will take precedence over from and to.
Sorting
You can also specify sort fields on most list endpoints:
| Parameter | Type | Default | Description |
|---|---|---|---|
sort_by | string | created_at | The field to sort by (e.g., created_at, updated_at, timestamp). |
sort_order | string | desc | The direction of sorting. Supported values: asc, desc. |
Authentication
Authenticate Trasys Public API requests using an X-API-Key header generated in the dashboard, plus the 401 and 403 errors returned for invalid API keys.
Rate Limits
Trasys Public API rate limits (100 requests/minute per key), the X-RateLimit response headers, 429 handling, and best practices for high-volume integrations.