Skip to main content

Webhooks & API

Stream every event to your own systems and submit codes server-to-server.

The Webhooks & API capability streams campaign events to your own endpoints, and lets your systems send entries in.


*Webhook endpoints are registered under Settings → Webhooks.*


SENDING EVENTS IN

Post events server-to-server with your API key:

```

-H "x-api-key: ck_..." \

-H "content-type: application/json" \

-d '{"type":"code.submitted","campaignId":"cmp_...","msisdn":"+2348000000000","payload":{"code":"ABC123"}}'

```


API keys are secret — server-side only, never in a browser. Generate them under Settings → Developers.


HEARING OUTCOMES BACK

Configure endpoints under Settings → Webhooks. The events you can subscribe to include:

• submission.verified

• reward.sent

• draw.completed

• draw.revealed


Every request carries an HMAC-SHA256 signature of the body in the X-Chekintel-Signature header. Verify it against your signing secret before trusting the payload.


The signing secret is shown once, when you create the webhook. Copy it then — it is not displayed again, and you will need to rotate the endpoint to get a new one.


WHY BUILD THIS WAY

Your front end stays fully under your control while ChekIntel handles verification, payout, fraud screening and analytics. Your site simply becomes another channel, reporting alongside WhatsApp and USSD.


Use a sandbox environment to test the full round trip before pointing production traffic at it.

Did this answer your question?