Skip to main content
This is the path if you are wiring FreshTalent into Claude, Cursor, or an ATS / CRM / outreach tool. Recruiters stay in the dashboard quickstart.

Dashboard names vs identifiers

1

Get an API key

In the dashboard under API Keys, create a key. It is shown once.
Keep keys server-side. Never ship ft_live_… in a browser app or a public repo.
2

Run one search

Same query the recruiter typed, as compact JSON:
The response is { data, query, meta }. data is compact people. query is the structured filter that actually ran: save it for repeat people searches, or add data to a List. Target discovery uses a different schema and is not an exact replay of the graph search. See Search query compatibility.
3

Pick a surface

4

Push movement into the ATS

Poll GET /events?since=24h. Each row is one profile diff (Left company, Open to work, …) with the person slug and LinkedIn URL. Upsert by URL into Greenhouse, Ashby, Lever, HubSpot, or your sequencer.Full recipe: ATS, CRM, and outreach.

Copy-paste: Node

For a complete script with list creation, search results, checkpoints, and HTTP error handling, follow Build your first integration.

Next

Claude, Cursor, VS Code

Eight tools over https://api.freshtalent.ai/mcp. Host configs and a prompt that actually works.

ATS & CRM

Poll events, map stages, keep the CRM as source of outreach truth.

API reference

Playground for every public endpoint.

Auth, errors, limits

Keys, 401s, 300 req/min, Target slots.