Skip to content
KelkiDevelopers

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.

In one sentence. You find the trade (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

Three use cases

The flow

  1. The need. POST /trade-matches with the need in everyday words: offer the first 2 or 3 trades to the person.
  2. The choices. GET /trades/{trade_id}: services and timings (closed lists), consent text in force.
  3. The place. GET /places?q=Créteil: an existing place, for example fr-creteil-94000.
  4. The draft. POST /requests: nothing is sent; you get the summary and the consent text.
  5. The consent. You show the summary, then the consent text word for word, with an unticked box; the person ticks it.
  6. The confirmation. POST /requests/{request_id}/confirmation (email method): Kelki e-mails the person; their click sends the request.
  7. Tracking. request.status_changed webhook: 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.