https://api.novig.com/nbx/v2.
You don’t have to move. v2 keeps working, and moving is your choice. Stay on v2 if it serves you well.
Check what v3 can’t do yet
v3 has lower rate limits
v2 limits each route by requests per second. v3 limits each subaccount with a bucket of tokens. The bucket holds a burst, then refills at a fixed rate.
A v3 batch spends one token per order, not one per request.
Each subaccount has its own buckets, and you can open up to . Extra keys on one subaccount don’t add capacity.
Higher limits are coming soon. We’re adding dynamic rate-limit tiers, with higher limits than the ones above. Until then, you can stay on v2.
GET /v3/limits returns the numbers that apply to you.
v3 has no RFQ routes
v3 doesn’t send or answer requests for quote (RFQs), our parlay pricing auction. If you price RFQs, keep that integration on v2. It keeps working as it does today. RFQ describes the v2 flow.What changes
- You sign each request. We store only your public key, so your private key never leaves your machine. Sign a request explains the rules.
- A trading key reaches one subaccount. Each subaccount has its own balance, positions, and orders. Account model shows how they fit.
- You can test on Paper first. Paper is our play-money exchange, with the same API as Production. Environments has the hosts.
Move step by step
You can move one strategy at a time. Your v2 credentials keep working while you test v3.1
Try v3 on Paper
Create a management key on Profile on paper.novig.com, then run the Quickstart.
2
Register a management key
Sign
POST /v3/keys with your v2 client-credentials token. The steps are below.3
Open a subaccount
Call
POST /v3/account/subaccounts with your management key. The reply creates the subaccount’s trading key.4
Fund the subaccount
Move money into it with a transfer. Funding shows how.
5
Move your order flow
Point one strategy at v3, and watch your throttle use with
GET /v3/limits.Register a management key with your v2 token
As a v2 LP, you can create your v3 management key with the client-credentials token you already use. You don’t need the web app for this. Get a token the way you do for v2, then generate a keypair:201 reply carries your keyId and "scope": "management". Save the keyId with novig-mgmt.pem. Every signed call needs both.
A 409 MANAGEMENT_KEY_EXISTS means you already hold a live management key. Use that key, or revoke it first.
Map your v2 routes
The API Reference lists every v3 route.

