Skip to main content
Blaaiz sends these events when an admin changes an auto-deposit registration to ACTIVE or BLOCKED. The events apply to registrations from both the dashboard and the API.

​
Events and destination

Your business must have API services enabled, a configured webhook URL, and a webhook signing_secret. Blaaiz sends the event to collection_url. If collection_url is null, Blaaiz uses payout_url. A repeated status does not send another event. Changes to PENDING or PROCESSING do not send these events. Removal of an ACTIVE registration also sends auto_deposit_email.blocked. After removal, the registration no longer appears in the read endpoints.

​
Payload

The payload is a flat object. The event name is in type; there is no event field or data wrapper.
For a blocked registration:
These payloads do not include the registration ID, transaction details, or a payment amount. A registration status event does not mean that a customer sent funds. See CAD collection webhooks for payment notifications.

​
Signature verification

Verify x-blaaiz-signature before you process the payload. Blaaiz signs the timestamp from x-blaaiz-timestamp, followed by a period and the JSON payload, with HMAC-SHA256. Use your webhook signing_secret, not the OAuth client_secret. See Signature verification for examples.

​
Delivery and status recovery

These registration events use synchronous delivery. They do not use the queued webhook log and replay flow. Automatic retries, delivery logs, and replay endpoints are not available for these events. Return a 2xx response when you accept an event. Store the event_id to avoid duplicate processing in your system. If you miss an event, read the registration to check its current status. The list endpoint also returns the current status.