# 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 - [Quickstart](https://kelki.ai/developers/en/quickstart/): six calls, from the trade to the webhook, in the sandbox. - [Concepts](https://kelki.ai/developers/en/concepts/): request lifecycle, draft and consent, a single professional. - [Consent of the person](https://kelki.ai/developers/en/consent/): read this page before any integration. - [Authentication](https://kelki.ai/developers/en/authentication/), [API reference](https://kelki.ai/developers/en/reference/), [errors](https://kelki.ai/developers/en/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](https://kelki.ai/developers/en/guides/concierge/)). - 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](https://kelki.ai/developers/en/guides/agent/)). ## The flow - The need. `POST /trade-matches` with 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 example `fr-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` (`email` method): Kelki e-mails the person; their click sends the request. - 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](https://kelki.ai/developers/en/terms/), the [data processing agreement](https://kelki.ai/developers/en/terms/data-processing/) (GDPR article 28) and the [acceptable use policy](https://kelki.ai/developers/en/terms/acceptable-use/). The French versions prevail. ## About this page - URL : https://kelki.ai/developers/en/ - Language : en - fr : https://kelki.ai/developers/fr/ - en : https://kelki.ai/developers/en/ - x-default : https://kelki.ai/developers/ - Portal : https://kelki.ai/developers/llms.txt