Bring the Kelki Agent into your app
One click in your app, and the person gets a call back from a professional of the right trade. The API applies exactly the rules of the kelki.ai “Call me back” form and of the MCP connector: same lists, same checks, same confirmation by the person.
The API is free for partners.
POST /trade-matches), show its services and timings (GET /trades/{trade_id}), check the place (GET /places), prepare a draft (POST /requests) that you show to the person with the consent text, then start the confirmation (POST /requests/{request_id}/confirmation). The person receives the “Confirm my request” e-mail: after their click, the request goes to the professionals of their area. Or the Kelki Agent leads the conversation (/agent/conversations).API address: https://kelki.ai/api/v1. Resources and fields in English; values (trades, services, timings, texts) in the requested language.
Where to start
- Quickstart: six calls, from the trade to the webhook, in the sandbox.
- Concepts: request lifecycle, draft and consent, a single professional.
- Consent of the person: read this page before any integration.
- Authentication, API reference, errors.
Three use cases
- Concierge service: a leak or a stuck lock in a short-let flat; a “Find a professional” button in the app (guide).
- Property management: the tenant reports a problem; the request goes out with the unit's reference, tracking comes back by webhook.
- Assistant: your conversational assistant hands the need over to the Kelki Agent (guide).
The flow
- The need.
POST /trade-matcheswith the need in everyday words: offer the first 2 or 3 trades to the person. - The choices.
GET /trades/{trade_id}: services and timings (closed lists), consent text in force. - The place.
GET /places?q=Créteil: an existing place, for examplefr-creteil-94000. - The draft.
POST /requests: nothing is sent; you get the summary and the consent text. - The consent. You show the summary, then the consent text word for word, with an unticked box; the person ticks it.
- The confirmation.
POST /requests/{request_id}/confirmation(emailmethod): Kelki e-mails the person; their click sends the request. - Tracking.
request.status_changedwebhook:transmitted,sold(taken by a single professional),called_back.
What you never receive
Neither a professional's contact details nor their identity, nor the person's contact details in clear (they come back masked: C•••, +33 6 •• •• •• 42), nor where requests came from. Kelki sells no data to the partner.
Countries and languages
Covered countries, their languages and their availability are read with GET /countries: live (requests accepted) or preparing (catalog readable, requests refused with country_not_available).
Terms
Use of the API is governed by the API terms of use, the data processing agreement (GDPR article 28) and the acceptable use policy. The French versions prevail.