Overview
Webhooks let you subscribe to Subtotal system events and receive real-time HTTP requests when those events occur. Use webhooks to keep your systems in sync with connection and purchase activity.Properties included with every event
These properties are included with each webhook request:
Below are all supported event types and their corresponding payload structures.
connection.activated
Connections areactivated when a customer successfully links their account.
Example
connection.activated event
connection.unauthenticated
Connections move fromactivated to unauthenticated when a customer needs to re-authenticate their account. For example, when a customer changes their password with the retailer.
Example
connection.unauthenticated event
connection.disconnected
Connections move todisconnected status when a customer disconnects their account.
Example
connection.disconnected event
connection.profile.created
Sent the first time Subtotal captures a consumer’s profile for a connection — their identity details from the linked retailer account, together with purchase metrics scoped to your brands.Unlike the other
connection.* events, the profile payload is flat: its fields sit directly under payload, not under payload.connection.Profile events are only delivered for active connections. While a connection is
unauthenticated or disconnected you will not receive profile events for it; if the profile changed in the meantime, the connection receives a single catch-up event when it is re-linked (alongside connection.activated).
Example
connection.profile.created event
connection.profile.updated
Sent when a previously captured profile changes — for example an updated email or postal code, or when new purchases shift the brand-purchase metrics. The payload is identical in shape toconnection.profile.created. Like connection.profile.created, this event is only delivered while the connection is active; changes that happen while a connection is unauthenticated or disconnected arrive as one catch-up event on re-link.
Example
connection.profile.updated event
purchase.created
Thepurchase.created event is sent when a new purchase is received from a customer’s connected retailer account.
We recommend using this event when you need to process customer purchases for your use case.
Example
purchase.created event