Register an endpoint
Response
Event subscriptions
Subscribe with specific event types, segment wildcards, or a mix:- Exact —
compliance.status_changed - Segment wildcard —
compliance.*,kyc.*,self_service_invitation.* - Root wildcard (
*) — not supported, for safety
Partner filtering
OptionalpartnerIds array scopes deliveries to specific authorized
partners. Omit (or send null) to receive events for all authorized partners
on this endpoint. Useful for marketplace integrators routing events per
dealer to different downstream systems.
Delivery request format
Every delivery is a POST with: Headers:
Body (envelope + data):
Idempotent processing
Deliveries are at-least-once. You may receive the same event more than once (retries after network blips, manual replays). Deduplicate on the eventid:
2xx status when you’ve successfully recorded the event,
even if your downstream processing hasn’t finished. Process the event
asynchronously after acknowledging.
Retry policy
NT24 retries failed deliveries with exponential backoff — up to 10 attempts over 72 hours (1m, 5m, 15m, 1h, 4h, 8h, 16h, 24h, 36h, 48h). After 20 consecutive failures OR 72h of continuous failure, the endpoint is auto-paused. You receive awebhook.endpoint_auto_paused
meta-event (delivered to any other active endpoint you have) and an email
to your organization admin. Individual events that exhausted retries emit
webhook.delivery_failed_terminal.
Resume a paused endpoint via PATCH /v1/webhooks/{id} with
status: ACTIVE.
Testing without live events
Fire a synthetic test event with any payload:Delivery history and replay
List the last 30 days of deliveries:Next
Signature verification
Validate
X-Novatrade-Signature before trusting the payload.Event catalog
All 10 event types with payload schemas.