Guide: affiliate program with the API
Your Kelki partner account is also an API account. Requests created with your live credentials automatically carry your partner code (KA-…): you earn 20% of the pre-tax price of each request bought by a professional, exactly as with the embedded modules.
How it works
- One account. The partner account (code
KA-…) and the API account (acc_…) are the same account. Your partner space gives you your developer secret, which opens the developer space: test keys first, live keys once Kelki has approved them. - Nothing to add. A request created with
POST /requestsand then confirmed by the person (“Confirm my request” e-mail) carries your code. Agent conversations (/agent/conversations) too: their request goes through the same confirmation. - Tracking. Your requests, their statuses and your commissions are shown in your partner space, without any personal data.
Optional Kelki-Affiliate header
To state it explicitly in your calls, send your code in the Kelki-Affiliate header. It must be YOUR account's code: any other code returns 403 insufficient_scope.
curl -X POST https://kelki.ai/api/v1/requests/req_01JC…/confirmation \
-H "Authorization: Bearer kk_live_…" \
-H "Kelki-Affiliate: KA-1042" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: 3f1c…" \
-d '{"method": "email", "consent_given": true, "consent_text_version": "v2026-10-18"}'
Commission rules
- Commission on requests bought and paid by a professional: 20% of the pre-tax price, in the currency of the sale.
- Pending for 30 days after the sale, then approved; monthly bank transfer from €50, on a self-billed invoice.
- The same person (phone or e-mail) counts once over 30 days, all channels; the sandbox (
kk_test_) never creates a commission. - The consent text, e-mail confirmation and per-contact limits remain those of the API: consent of the person.
The copy-and-paste modules and the program terms (in French, which prevails): partner program, terms.