Webhooks and integrations

Connect provider events and downstream systems with explicit delivery semantics.

Receive provider lifecycle events, record trusted outcomes through the API and deliver signed outbound events with durable retry evidence.

01ReferralLink or code
02ConversionStable event
03CommissionRule evidence
Signed deliveryDurable retriesEnvironment scoped

Built for operating reality

Clear contracts at every boundary.

01

Verify before parsing

Webhook consumers can authenticate the exact raw body and timestamp before application code trusts its contents.

02

Retry with stable identity

Provider event IDs and delivery records prevent a redelivery from becoming a second business action.

03

Keep credentials bounded

Provider connections, API keys and endpoints remain scoped to the tenant application environment they serve.

Inbound events

Translate provider lifecycles into canonical outcomes.

Environment-specific endpoints authenticate supported provider events and map them to stable users, purchases, refunds and subscription identities before business rules run.

Outbound delivery

Make downstream delivery observable and replayable.

Endpoint subscriptions, signed bodies, attempt history and bounded retry state give tenant systems a durable event contract rather than a best-effort callback.

Questions, answered

Know where the boundaries are before you integrate.

How should an outbound webhook be verified?

Verify the signature and timestamp against the exact raw request body before parsing or acting on the payload.

What happens when a delivery times out?

The attempt remains observable and retries retain the same event identity; a timeout is not treated as proof that nothing happened.

Are provider credentials shared across environments?

No. Provider connections and their secret material are bound to a specific application environment.

Build the reliable path

Make every referral decision traceable from click to payout.

Request sandbox access