A token for the account
Each token belongs to one teammate. Calls can read or change only what that role allows, and only in the projects they can open.
Updated October 18, 2026
On Team and above, Klientr answers JSON at /api/v1. Send Authorization Bearer and a token that starts with kl_. The response follows that teammate's role.
Starter leaves the API off. Team, Business, and Studio include it. Create the token in settings. It is shown once.
Each token belongs to one teammate. Calls can read or change only what that role allows, and only in the projects they can open.
Send X-Project-Id, or project_id, when the token can see more than one project. The call then stays in that project.
Contacts, conversations, replies, tasks, bookings, services, articles, the FAQ bot, feedback, campaigns, social mentions, teammates, and project settings.
On Team or above, open settings and create an API token. Copy it then. It is not shown again.
Send HTTPS JSON with Authorization Bearer and the kl_ token. Add X-Project-Id when the workspace has more than one project.
The API docs page lists every path, with the request and the response. The same page is linked from the site footer.
REST API Swagger documentationThe same workspace, from a different question.
Create a free workspace, connect a channel, and keep the reply, the booking, and the follow-up together.
No credit card · Your workspace, your data · Invite the team later