GET /webhooks · POST /webhooks

Webhook endpoints

An endpoint subscribed to compliance.status_changed is the answer to polling the rollup: the API calls the partner when the verdict moves, instead of the partner asking. This demo registers endpoints and lists them. It does not receive deliveries — there is no public URL here to deliver to, and a signature verifier nothing can call would be a claim rather than a demonstration.

Registered — GET /webhooks

HTTP 404

The list carries no signing secret. The contract returns it on the create response only, so there is no call that reads one back — which is why the registration below shows it once and this list never can.

Register — POST /webhooks

A WebhookEventSubscription is an event type or a segment wildcard — compliance.*, kyc.*, self_service_invitation.* — and the contract does not support a root *. Subscribing to everything is not something the API offers a shorthand for.

  • compliance.status_changed
  • compliance.decision_made
  • kyc.vies_check_failed
  • kyc.verification_completed
  • export_file.generated
  • prospect.submitted
  • self_service_invitation.used
  • self_service_invitation.expired
  • webhook.endpoint_auto_paused
  • webhook.delivery_failed_terminal
partnerIds (optional)

Tick the sellers whose events should fire on this endpoint. Ticking none sends no partnerIds at all, which the contract reads as every authorized partner. The list is GET /me's authorizedPartners, and a uuid that is not in it is refused before the call.

Submitting registers a real endpoint against whatever NT24_API_BASE_URL points at, with an Idempotency-Key minted server-side for this attempt. Changing or removing one needs PATCH or DELETE /webhooks/{id}, which this demo does not call.