Consent of the person
Read this page before any integration. No request is sent unless the person has seen the summary, accepted the consent text, then confirmed their request by e-mail themselves. The API enforces it technically.
The three steps
- The summary. After
POST /requests, displayrecap: trade, service, timing, place, contact details. - The consent text, word for word. Display
consent.textas returned by the API, without changing, shortening or translating it, next to a checkbox left unticked by default, separate from your own terms and from any other box. Then sendconsent_text_version(the version shown) andconsent_given: true. - Confirmation by e-mail.
POST /requests/{request_id}/confirmationwith"method": "email": Kelki sends the person the “Confirm my request” e-mail, which names your app. The request is sent only after their click on the button of the confirmation page.
The consent text in force
Version v2026-10-18, in French — the text is returned by the API in the language of the request and must be displayed exactly as returned:
(Meaning: “I agree that my request and my contact details be sent to one or more professionals of the trade in my area, who may call me back about it.” This gloss is for your understanding only; never display it instead of the text returned by the API.)
The text to display for a request is always the one of its draft (consent); versions are dated and immutable (GET /consent-texts/{version}). If the version changed between the draft and the confirmation, the confirmation is refused (consent_version_outdated): display the new text and ask for consent again.
Confirmation by e-mail
- The e-mail is sent in the language of the request and names your app (name set by Kelki, without link or address, to prevent phishing).
- The link opens a kelki.ai page that shows the summary; only the button on that page confirms. A link preview by a messaging app confirms nothing.
- The link is valid for 48 hours. Without a click, the request becomes
abandonedand its contact details are erased. - The link is never returned to the partner. You cannot confirm on the person's behalf, and you must not try to.
- In the sandbox, no e-mail is sent: sending is simulated.
At launch this is the only method: no consent attestation by the partner is accepted.
Informing the person
Next to the send button, in addition to the consent text, display the notice of annex 1 of the data processing agreement, with the link to Kelki's privacy policy.
Limits shared by all channels
At most 3 requests per 24 hours for the same phone number or e-mail address, across all Kelki channels (form, MCP connector, Agent, API): beyond that, contact_limit_reached. Suggest the person confirm the requests already received by e-mail. An identical request already pending is not created again and does not trigger a new e-mail.
Compliant and non-compliant screens
| Compliant | Non-compliant |
|---|---|
| Full summary, then the exact consent text, empty box, “Send my request” button. | Box pre-ticked, or ticked by your code. |
| Consent box separate from your terms and conditions. | A single box “I accept the terms and the transmission”. |
| Consent text shown in full, readable, in the language of the request. | Text summarised, translated by you, hidden behind a link or in small print. |
| The person enters or checks their own contact details. | Request sent for someone else without their express permission. |
| Clear message after sending: “Check your inbox to confirm”. | Countdown, pressure, commercial offer mixed with the request. |
These rules are those of the API terms (article 5) and of the acceptable use policy.