Skip to main content
PROD URL: https://api.novig.com/nbx/v2 QA URL: https://api-qa.novig.us/nbx/v2

​
Rate Limits

Each limit is per route and per method. A row that lists several routes gives each of them its own budget at that limit: every cancel route has its own 1024 requests per second, and single-order placement no longer competes with batch placement. User history endpoints support a maximum limit of 1024 items per request for /orders and 256 items per request for /fills and /transactions (default 100).

​
Rate limit responses

When a limit is exceeded the API responds with HTTP 429 Too Many Requests. Every response (both 2xx and 429) carries rate-limit headers:
Retry-After and X-RateLimit-Reset are reported in milliseconds, not seconds. A value of 73 means wait 73 ms, not 73 seconds. Do not feed these values into helpers that assume the HTTP-standard seconds unit.
Endpoints with a two-tier burst + sustained policy (the user-history endpoints) emit a separate set of headers per tier, suffixed with the tier name — e.g. X-RateLimit-Remaining-burst and X-RateLimit-Remaining-sustained. Honor whichever tier is closest to its limit. We recommend retrying on 429 after the Retry-After delay with exponential backoff. Timeout: 5 seconds

​
Features

  • Place, cancel, and query orders
  • Retrieve market data and positions