Version: 3.0.0
NAS Card Issuing Webhook Events
Events are sent as HTTP POST requests to the callback URL registered for your client, one request per event.
Envelope
Every event has the same fields: id (unique per event), eventType, apiVersion (v3), code, message, createTime (milliseconds since the epoch, as text) and resource. The resource field is a JSON document carried as a string, and its contents depend on the event type.
Verifying a delivery
Each request carries these headers:
Signature-Method:HMAC-SHA256.Signature: Base64 HMAC-SHA256 of theresourcestring, using the webhook secret issued to your client. Compute it over the exactresourcestring and compare.Timestamp: when the attempt was sent, in milliseconds since the epoch. Each retry carries its own.X-NAS-Signature,X-NAS-Signature-TimestampandX-NAS-Signature-Headers: a second signature covering the whole body and the send time, with one value per active secret while a secret is being rotated.
Reject a delivery whose signature does not match.
Handling deliveries
- Answer with a 2xx status quickly. Any other answer, or no answer, is treated as a failure and the event is sent again later.
- The same event can arrive more than once. Use the
idto ignore repeats. - Events can arrive out of order. Use
createTimeand the state in theresourcerather than the arrival order.
Only the event families below are sent.