> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apexiumbet.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Limits - Rate limits and request limits

> Per-key rate limits of the Apexium API, the per-address limit of the health check, the throttling of failed authentication, the size limits of orders, cancellations and listings, and the WebSocket limits.

## Rate limits

Each key has three budgets, counted over one minute:

| Budget | Endpoints | Requests per minute |
| - | - | - |
| Placements | `POST /v1/orders`, previews included | 600 |
| Betslip | `GET /v1/betslip` | 60 |
| Everything else | every other endpoint, market data included | 600 |

Cancellations count against no budget: `POST /v1/orders/{id}/cancel` and `POST /v1/orders/cancel-all` are not rate-limited per key, so you can always pull your orders.

The budgets are separate: reading orders does not consume the placement budget. Over a budget, requests get `429 RATE_LIMITED` with these headers:

| Header | Meaning |
| - | - |
| `retry-after` | Seconds until the budget refills |
| `x-ratelimit-limit` | Requests allowed per minute |
| `x-ratelimit-remaining` | Always `0` on a refusal |
| `x-ratelimit-reset` | Seconds until the budget refills |

Wait `retry-after` seconds before you retry. To place many orders, spread them over the minute rather than bursting.

## Health check

[`GET /v1/health`](https://docs.apexiumbet.com/api-reference/overview#health) carries no key, so it has its own budget per address: 120 requests per minute. Over it, requests get the same `429 RATE_LIMITED` and headers. Its result is refreshed at most every 15 seconds, so polling every 15 seconds is enough.

## Failed authentication

After 20 failed authentications from the same address within one minute, every request from that address gets `429 RATE_LIMITED` until the minute ends, whatever key it carries. A client that retries with a revoked key can lock itself out this way: check the key first. See [Authentication](https://docs.apexiumbet.com/api-reference/authentication.md#failed-authentication).

## Request limits

| What | Limit |
| - | - |
| `clientOrderId` | 1 to 200 characters, unique per account |
| `bookmakers` on an order | 1 to 50 |
| `stake.amount` | positive, at most two decimals |
| `minPrice` | at least 1.001, at most four decimals |
| `expiresAt` | in the future, at most one hour ahead |
| `POST /v1/orders/cancel-all` | 200 orders per call; continue with `nextCursor` |
| `GET /v1/pnl` window | at most 366 days |

Your account also has its own limits, such as a maximum stake per fixture. They are applied to every order and shown by [`GET /v1/betslip`](https://docs.apexiumbet.com/api-reference/overview#betslip).

## WebSocket

| Limit | Value |
| - | - |
| Connections per API key | 8 |
| Fixtures per account, summed over its connections | 500 |
| Betslip selections per account, summed over its connections | 50 |
| Send buffer of a connection that reads too slowly | closed with `4002` above 4 MB, or when not empty for more than 5 seconds |

Over the connection, fixture or selection limit, the server refuses with `4004 limit_exceeded`. See [Close codes](https://docs.apexiumbet.com/websocket/close-codes.md#4004) for what each code means and what to do.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.