General Payload Structure

webhook payload structure standard payload format every webhook delivery contains a json object with the following structure { "webhookid" 123, "events" \[ { "id" 45678, "createdat" "2026 01 22t10 15 30 123456z", "type" "transactions credits created", "data" { "state" "requested" "transactionid" "41fc05d5 3148 4ee2 bfdf 9ad5ab7172c6" } }, { "id" 45679, "createdat" "2026 01 22t10 16 45 789012z", "type" "transactions debits created", "data" { "state" "requested" "transactionid" "41fc05d5 3148 4ee2 bfdf 9ad5ab7172c7" } } ] } payload fields field type description webhookid integer the internal id of the webhook configuration that triggered this delivery events array array of event objects (1 to max batch size events) event object structure each event in the events array contains field type description id integer unique, monotonically increasing event id createdat string iso 8601 timestamp with microsecond precision type string event type identifier (see event types reference) data object event specific data payload (structure varies by event type) http headers every webhook request includes header value description content type application/json payload format authorization bearer \<jwt> signed jwt token for authentication if you configured a callback api key , it will be included in an additional header (check your implementation for the specific header name) event ordering events within a batch are ordered ascending by their id field event ids are never skipped or reused, guaranteeing a clear sequence the last sent event id field on your webhook configuration always reflects the highest event id successfully delivered batch size a webhook delivery contains between 1 and max batch size events the actual number depends on how many undelivered events are available whether max wait seconds elapsed before max batch size was reached