Docs

Send us a conversion.

Two ways in: post to the conversion API yourself, or connect Stripe and let invoice events do it. Both are idempotent, so retries cannot double-credit.

Conversion API

Authenticate with an API key from your dashboard. external_order_id is the idempotency key — send the same one twice and the second call is rejected as a duplicate rather than creating a second commission.

POST /api/v1/conversions
Authorization: Bearer <api-key>
Content-Type: application/json

{
  "click_id": "<the reign_click cookie from your own domain>",
  "external_order_id": "ord_10482",
  "amount_cents": 4999,
  "currency": "GBP",
  "customer_email": "buyer@example.com",
  "occurred_at": "2026-07-28T10:22:04Z"
}

click_id is the reference we appended to your landing URL as ?rgn= and our snippet stored first-party on your domain. Send it in the body, or on the X-Reign-Click header. Omit it and the sale is recorded, accepted, and attributed to nobody — why that is.

How a commission is worked out

Attribution

The click is resolved from the click_id you returned, scoped to your own account, then widened to the other clicks sharing its fingerprint. A coupon code can take priority where the programme allows it. Everything is judged inside the programme's click window.

Calculation

The programme's commission rules are applied — percentage, fixed or tiered, with per-plan overrides and lifetime-volume tiers.

Accrual

The commission and its double-entry ledger accrual are written in a single transaction. Neither can exist without the other.

Hold and release

Commissions sit pending until the auto-approve window passes, then become payable.

Refunds

A refunded conversion voids the commission and posts a reversing ledger entry. The original accrual stays on record.

Get an API key How it works →