Webhooks

Webhook payloads

The fields each kind of event carries.

Creator events

Creator events carry event, occurred_at, campaign_affiliate_id, campaign_id, organization_id, user_id and status, and, when we have them, campaign_name, organization_slug, user_email, user_name and tag.

campaign_affiliate.activated

{
  "event": "campaign_affiliate.activated",
  "occurred_at": "2026-11-01T15:04:05Z",
  "idempotency_key": "e3b0c442-98fc-4c14-9afb-f4c8996fb924",
  "campaign_affiliate_id": 4096,
  "campaign_id": 512,
  "campaign_name": "Spring launch",
  "organization_id": 1024,
  "organization_slug": "example-brand",
  "user_id": 77,
  "user_email": "creator@example.com",
  "user_name": "Example Creator",
  "status": "active",
  "tag": "MAYA15"
}

Sale events

Sale events add affiliate_sale_id, order_id, total_cents, subtotal_cents, commission_cents, currency (lower case), platform (shopify, website, ios or android), sale_type, sale_occurrence (initial for the customer's first credited sale, recurring after) and the payout status.

Sample events

Sample events carry organization_id, organization_slug and the whole sample_request, as GET /sample_requests/{id} returns it at delivery time.

Attribution

A creator who came in through POST /campaign_applications also gets an attribution object on their events: the click ids, UTM values, your own id and the TikTok details you sent with them. Never the browser's IP address or user agent.