Pagination - Tradara

Every list endpoint returns at most limit rows plus a next_cursor field. Use that cursor to fetch the next page; stop when it is null or absent.

Request shape

GET /v1/orders?account_id=<uuid>&limit=100&cursor=<opaque>

Parameter	Type	Notes
`limit`	integer	Page size. Default 100, max 1000 per endpoint unless noted.
`cursor`	string	Opaque token from the previous response. Omit on the first call.

Cursors are opaque — do not parse them, decode them, or store them long-term. They embed both the position and any active filters; replaying a cursor with different filters returns 400.

Response shape

{
  "data": [ /* up to `limit` rows */ ],
  "next_cursor": "eyJrIjoiMTcwOTk5MjAwMDAwMCJ9"
}

When next_cursor is null or missing, you have reached the end of the result set.

Iterating a list

cursor=""
while :; do
  url="$TRADARA_BASE_URL/v1/fills?account_id=$ACCOUNT_ID&limit=500"
  [ -n "$cursor" ] && url="$url&cursor=$cursor"

  resp=$(curl -s "$url" -H "X-Tradara-Api-Key: $TRADARA_API_KEY")
  echo "$resp" | jq '.data[]'

  cursor=$(echo "$resp" | jq -r '.next_cursor // empty')
  [ -z "$cursor" ] && break
done

Time-range filters

Fills, trades, and balance snapshots accept from_ts and to_ts Unix-millisecond filters. Combine them with cursor pagination to backfill long ranges:

GET /v1/fills?account_id=<uuid>&from_ts=1735689600000&to_ts=1735776000000&limit=1000

The range is inclusive on both ends.
to_ts must be greater than from_ts.
Without a range, list endpoints default to the most recent rows (typically last 24 hours).

Ordering

Within a single result set, rows are ordered by their primary timestamp descending (newest first) unless an endpoint documents otherwise. Daily history endpoints (e.g. GET /v1/accounts/{id}/positions/daily) order ascending by date.

Per-endpoint defaults

Endpoint	Default `limit`	Max `limit`
`GET /v1/orders`	100	500
`GET /v1/fills`	100	1000
`GET /v1/trades`	100	500
`GET /v1/balances/{account_id}/snapshots`	100	365
`GET /v1/firm-control/users`	50	200
`GET /v1/firm-control/staff`	50	200
`GET /v1/admin/query/*`	50	200

Requesting limit above the maximum returns 400.

Offset pagination (legacy)

A small number of administrative read endpoints under /v1/admin/query/* accept page and page_size instead of cursor. Where both are supported, prefer cursor pagination — offset queries become expensive on long histories and are not guaranteed to be stable across writes.

​Request shape

​Response shape

​Iterating a list

​Time-range filters

​Ordering

​Per-endpoint defaults

​Offset pagination (legacy)