Novig API: what it exposes, how it authenticates, where it stops

What the API exposes

REST production is https://api.novig.com/nbx/v2 with QA at https://api-qa.novig.us/nbx/v2, both in AWS us-east-1. Endpoints cover placing single and batch orders (maximum 256 per batch), cancelling by ID, batch or all, a kill switch, fills, positions, open markets, order books, markets by event, lock status, tick tables, strike requests, leagues, event types, events, wallet balance, open costs and transaction history.

The WebSocket at wss://api.novig.com/tape exposes a global tape channel, per-market book channels, a lifecycle channel (OPEN, END, CLOSE, START, EVENT_GOLIVE, EVENT_UNLIVE) and a private channel for your own place, fill and cancel updates. The server pings every 15 seconds and disconnects a client that misses a full interval.

Two anonymized CSVs per trading day (every trade and every market snapshot) are published at data.novig.com with no API or authentication, and a maker credit program pays cash credits for liquidity on live markets.

Authentication and rate limits

Auth is OAuth 2.0 client credentials: POST to https://api.novig.com/nbx/v1/auth/emm-token with your client ID and secret, then send Authorization: Bearer on every call. Tokens expire 30 minutes after issuance.

Published limits per interval: order placement 64 per second, batch placement 64 per second, order cancellation 512 per second, kill switch 1 per 30 seconds, user history endpoints 32 burst per second and 512 sustained per 60 seconds, everything else 256 per second. Exceeding a limit returns 429 with X-RateLimit headers; Retry-After and X-RateLimit-Reset are in milliseconds, not seconds. Request timeout is 5 seconds.

Pricing and access

No API fee. You request a client ID and secret from Novig; the GraphQL page directs new users to developers@novig.co.

The trading fee is P x (1 - P) x 0.03 x contracts, charged on live taker fills of straight contracts, exact to five decimals with no minimum. At P = 0.50 that is $0.0075 per $1.00 contract. The API's qty field is in hundredths, so 100 qty equals one contract.

Where it falls short

There is no self-serve key. Credentials come from the Novig team, and PrivateLink is not offered.

The GraphQL API, the only endpoint that needs no auth, is being sunset, so read-only integrations must migrate to NBX credentials.

Coverage is sports only, and the qty and millisecond conventions are easy to get wrong by a factor of 100 or 1,000.

Who should use it

Market makers and quant desks trading US sports who want deterministic limits and a documented fee formula.

Casual users who only want odds are better served by the daily CSV dumps than by applying for API credentials.