POST /rfq/pricer; Novig mints your shared secret and hands it back in the response. Once registered, POST /rfq/pricer/ping lets you verify reachability and signature handling before any live quote flow.
Authentication
Both endpoints use the same OAuth 2.0 Client Credentials token as the rest of the API — see Authentication. Send it as a bearer token:Prerequisites
1
You're onboarded as an LP
You must already be an LP. If you aren’t, follow LP Onboarding first. Registration links to that LP
account via your access token.
2
Your webhook is reachable
The base URL you register must be reachable from the public internet. For local development, terminate
https at a tunnel
like ngrok and register the public URL.POST /rfq/pricer — register or re-point your webhook
Register your pricer webhook, or re-point an existing registration at a new URL.
- First call creates your pricer and mints a fresh 32-byte shared secret.
- Later calls re-point the URL and keep the existing secret — the secret only ever changes on first registration.
Request body
Response
200 OK:
Your shared secret
Novig mints the shared secret server-side — a 32-byte key, hex-encoded as 64 lowercase characters — on your first registration. The same value lives on both sides: Novig signs every webhook body with it, and your pricer verifies. You never choose or upload it; you read it from the registration response.POST /rfq/pricer/ping — verify connectivity
Ask Novig to send a signed test request to your registered webhook and report how it answered. Use it to confirm reachability and that your signature verification works — before any live quote flow depends on it.
Novig reads your pricer straight from the database rather than a cached snapshot, so a registration made seconds ago is immediately pingable. The signed request lands at <webhookUrl>/ping — see Webhook Signing and the /ping handler you implement.
Response
200 OK:
A
404 from this endpoint means the calling LP has no registered pricer yet — register with POST /rfq/pricer first.