Order API and refunds

Use Settings → Tracking → Revenue integration on your own website.

Create a server key

Choose Create revenue key. Copy the secret once and save it in your server environment as SEEAN_REVENUE_SECRET. Use the endpoint displayed under Integration examples. The site ID in the payload is the website’s internal ID, not its tracking token.

Send Authorization: Bearer <SEEAN_REVENUE_SECRET> and Content-Type: application/json. Never put this key in browser code.

Order payload

After verifying payment with your provider, send:

{
  "siteId": "YOUR_SITE_ID",
  "type": "order",
  "externalId": "order-123",
  "amount": 2900,
  "currency": "USD",
  "product": "Your product",
  "kind": "one-time"
}

Amounts are USD cents. Subscription orders can use "kind": "subscription". Use a stable external order identifier and include optional attribution fields described in the overview.

Full refunds

Send to the same endpoint:

{
  "siteId": "YOUR_SITE_ID",
  "type": "refund",
  "externalId": "order-123"
}

Other currencies and partial refunds are rejected.

Retries and key rotation

Identical orders and refunds with the same externalId are deduplicated. Conflicting order data returns 409. Retry 429 or 503 later with the same payload and identifier.

Rotating the revenue key invalidates the previous key immediately. Update the server integration before expecting later orders to arrive. This is a custom server integration; provider webhook verification remains your responsibility.

Something unclear? Contact support.