Skip to main content
POST
Projects

Overview

Manage the seat’s hiring projects — the Recruiter equivalent of a lead list — and the candidates inside them. One endpoint, the action picks the operation. Uses the account’s Recruiter seat — see Connect Account. Pass the LinkedIn account’s account_id. Candidates come from Search People Recruiter.
Each action consumes 1 credit, list_project_candidates 1 credit per 10 results. Ignore this if you’re on per-seat pricing: usage is unlimited.

Request

string
required
Your API key for authentication.
string
required
The LinkedIn account’s id. Its Recruiter seat must be connected.
string
required
One of the actions below.
object
Depends on the action — see each one below.

Actions

  • candidate_urn is the candidate’s hire_identity_urn from the search; profile_urn is their profile_urn.
  • project_urn is the urn from list_projects / create_project (a project_id works too).
  • state takes the stage name as the project shows it ("contacted", "uncontacted"), its status type (CONTACTED…) or its urn from hiring_states. The stage shown as “uncontacted” has the status type SHORTLISTED.

Typical flow

  1. Search People Recruiter → keep the candidate’s hire_identity_urn.
  2. create_project { "name": "Growth Marketer — Paris" } → keep project_urn (or pick one from list_projects).
  3. add_to_project { "project_urn", "candidate_urn": <hire_identity_urn> } → the candidate lands in “uncontacted”.
  4. After contacting them, move_candidate with "state": "contacted".

Example