developers

Three calls.
That's the api.

send a reward, check a reward, hear about a claim. docs stub — the surface is deliberately this small. design partners get keys first.

01 / send a reward
  POST /v1/rewards
  {
    "value": 2500,            // minor units — £25.00
    "currency": "GBP",        // GBP · USD · EUR
    "recipient": "jo@example.com",
    "from": "Meridian Research",
    "message": "Thanks for completing our study."
  }

  → 201 { "id": "rwd_8kf2", "claim_url": "https://…/claim/WC8CFC3G", "status": "sent" }
02 / check a reward
  GET /v1/rewards/rwd_8kf2

  → 200 { "status": "claimed", "brand": "steam", "claimed_at": "2026-07-19T14:02:47Z" }
03 / hear about the claim
  WEBHOOK reward.claimed
  { "id": "rwd_8kf2", "campaign": "q3-panel", "value": 2500, "claimed_in_seconds": 47 }

  // also: reward.sent · reward.reminded · reward.refunded (90-day unclaimed)
04 / everything else

idempotency keys on every POST · bulk = one POST per recipient or a csv upload in the dashboard · zapier wraps all three calls for the no-code crowd · sandbox keys mint instantly, live keys after a hello.

GET SANDBOX KEYSSEE WHAT THE CLAIM_URL OPENS

← BACK TO THE REGISTER