Pagination
MyStocks list endpoints use cursor-based pagination — pass ?limit= and ?cursor=; every response carries hasMore and nextCursor so you never calculate offsets. Per-endpoint defaults and maximums included.
List endpoints use cursor-based pagination. Pass ?limit= to control page size and ?cursor= to
advance to the next page. Every paginated response includes hasMore and nextCursor so you never
need to calculate offsets.
Request parameters
| Field | Type | Required | Description |
|---|---|---|---|
| limit | integer | No | Items per page. Default and max vary by endpoint (see below). Clamped to the endpoint maximum if exceeded. |
| cursor | string | No | Opaque cursor returned as nextCursor in the previous response. Omit on the first request. Treat cursors as opaque strings — do not construct or parse them. |
Response fields
| Field | Type | Required | Description |
|---|---|---|---|
| count | integer | No | Number of items in this page (≤ limit). |
| hasMore | boolean | No | true if at least one more page exists. false means this is the last page. |
| nextCursor | string | null | No | Pass as ?cursor= on the next request. null when hasMore is false. |
Limit defaults & maximums by endpoint
| Endpoint | Default | Max |
|---|---|---|
GET /users | 100 | 500 |
GET /orders | 50 | 200 |
GET /users/{userId}/orders | 50 | 200 |
GET /users/{userId}/transactions | 50 | 200 |
GET /audit | 50 | 200 |
GET /webhooks/{id}/deliveries | 20 | 100 |
Fetching all pages — JavaScript
Cursor stability. Cursors are Firestore document IDs and remain valid indefinitely. New items inserted after your first request appear in subsequent pages if they sort after the cursor position — consistent forward-only iteration is guaranteed. Do not cache cursors across API-key rotations.