Skip to main content
The Embedded API is for companies that use Kalent through the API only, usually to offer talent search inside their own product to their own customers. Nothing here depends on the Kalent app: you send a request, you get profiles back, and what you do with them is up to your product.

​
What it covers

Talent search

Synchronous search by filters or by prompt. One credit per profile returned.

Qualified search

Asynchronous search that judges every matching profile green, amber, or red against your criteria. Two credits per judged profile.

LinkedIn contact enrichment

Verified email and phone for a LinkedIn profile URL.

​
What it assumes

  • An API key. Create it in the Kalent app under your workspace settings; see Authentication.
  • No Kalent subscription for search. Talent search and qualified search only need API credits, which the workspace owner can buy in Kalent billing. Contact enrichment still requires an active or trialing subscription.
  • Credits on that workspace. Talent search and qualified search spend API credits. LinkedIn contact enrichment spends contact credits.
  • Nothing else. You do not need to create sourcings or candidates in the Kalent app, and no recruiter has to log in.

​
Same key, same credits as the Platform API

The Platform API automates a workspace that a team also uses in the Kalent app: sourcings, candidates, and outreach sequences. Both APIs authenticate with the same workspace API key and share the same two credit balances, so you can mix them on one workspace. Start with the Embedded API if your users never open the Kalent app; start with the Platform API if they do.

​
Next steps

  1. Read Authentication and Non-deterministic results.
  2. Run your first POST /v1/search/talents, or import the Postman collection.
  3. When you need verdicts rather than raw profiles, move to the qualified search overview.