Configure delivery
Enter a public HTTPS Webhook URL, then select any of the currently supported event types:connection.activatedconnection.unauthenticatedpurchase.created
connections:read permits the connection events, and purchases:brand_products is required for purchase.created.

Identify the installing dashboard team
Partner deliveries addsubtotal_client_id at the top level. Use it to route the event to the correct brand in your system.
id is stable across delivery replays. Make handlers idempotent by deduplicating on that ID within the installing dashboard team.
Verify every request
Use the app’s signing secret to verify every delivery. See Verifying webhook signatures for the shared signing protocol and implementation guidance. Subtotal sends:
Compute the HMAC over the timestamp, one period, and the exact raw request body:
2xx response quickly. Parse JSON only after signature verification.
Rotate the signing secret
Use Rotate signing secret in Created Apps. Deploy the new value and keep the returned previous value as a verifier for no more than 24 hours. Pass both values insecrets during the overlap; afterward, remove the previous value.
Simulated events
Enable Receive simulated events to deliver events created through Subtotal’s Event Simulator to installed copies of this app. Leave it disabled if your endpoint should receive only non-simulated activity. When enabled, simulated events matching the app’s selected event types are sent to the same webhook endpoint as other events.Receive simulated events must be disabled for approved apps.