Two APIs, one key
Embedded API
Use Kalent through the API only, typically to offer talent search inside
your own product. Talent search, qualified search with green / amber / red
verdicts, and LinkedIn contact enrichment. No dependency on the Kalent app.
Platform API
Automate the workspace your team uses in the Kalent app: create sourcings,
add candidates, launch outreach sequences, and read their status back.
What you can do
Search talents
Find professionals matching complex criteria: job title, location, skills,
experience, education, and more.
Qualified search
Start an asynchronous search that evaluates matching profiles against your
criteria. Poll for green, amber, and red verdicts, or receive them on a
webhook.
Run your sourcings
Create sourcings, add candidates, and start outreach sequences in the
workspace your recruiters already use.
Non-deterministic results
Understand why search results may vary between identical requests and how to
work with this behavior.
Try it in Postman
Download the Kalent API Postman collection
Import this collection in Postman to try every endpoint: talent search,
qualified search, sourcings, candidates, contact enrichment, and dynamic
sequences. Set the
baseUrl and apiKey collection variables, then run the
requests in order.Base URL
All API requests are made to:Quick example
Rate limits and credits
Request windows, the 429 body, and both credit balances are documented on their own pages:- Rate limits — five windows per API key, and what a 429 looks like.
- Credits — API credits for search, contact credits for enrichment.

