Reference - Yellow Guide

Rate Limiting

Rate limiting is enforced to ensure fair usage:

All monetary and quantity values are represented as strings in decimal format to maintain precision:

{
  "amount": "1.50000000",
  "price": "35000.00000000"
}

Timestamps are provided in milliseconds since Unix epoch:

{
  "server_time": 1640995200000
}

Order UUIDs follow standard UUID format:

{
  "order_uuid": "550e8400-e29b-41d4-a716-446655440000"
}

List endpoints use cursor-based pagination. You walk through results by following the next_cursor returned with each page:

First page

— send use_cursor=true (and optionally page_size).

Read next_cursor and has_more from the response.

— send cursor=<next_cursor> from the previous response.

Repeat while has_more is true.

Query parameters

Parameter	Type	Description
`use_cursor`	boolean	Set `true` to use cursor pagination. Send it on the first request.
`cursor`	string	Opaque continuation token from the previous response’s `next_cursor`. Omit on the first page.
`page_size`	integer	Items per page. Default `50`, maximum `100`.

Response fields

Field	Type	Description
`next_cursor`	string	Token to pass as `cursor` for the next page. Empty when there are no more pages.
`has_more`	boolean	Whether another page exists.
`page_size`	integer	Items per page.

Always treat cursor values as opaque — do not parse or construct them. A malformed cursor returns 400 with "error": "invalid_cursor".