Skip to Content
InvyteDocs

Add someone to a Job

Put a Talent Hub person forward for a Job, by the key `talent.list` gave (an Invyte Network person's `person_v1.…` key works too). A member who said yes to roles like this joins the pipeline and is told; anyone else is asked first by email (members to say yes, others to join Invyte). Never sends when they declined this Job, asked not to be emailed about roles, or have no address: it is refused with the reason and what to do instead.

POST
/operations/pipeline.addPerson

Authorization

bearer
headerAuthorizationBearer <API key or OAuth token>

An organization API key (ink_live_…, ADR-0124), or the OAuth access token a person's AI client gets from the Recruiter MCP sign-in. Only the Authorization header is accepted.

Header Parameters

Idempotency-Key?string

Makes a write safe to repeat: the same key and input return the first result. Required for agents' writes and for anything a person confirms.

Match^[A-Za-z0-9._:-]+$
Length8 <= length <= 128

Request Body

application/json
  1. body
input*
confirmation?string

The id from a confirm or awaiting_approval Outcome, sent with the same input and key to go ahead.

Response Body

Done. A replay of the same key and input omits output.

application/json
  1. response
status*unknown
output?
replay?
actionId*string
Example Request
curl -X POST 'https://www.invyte.ai/api/recruiter/v1/operations/pipeline.addPerson' \  -H 'Content-Type: application/json' \  -d '{  "input": {    "jobId": "string",    "personKey": "string",    "channel": "YOUR_TALENT_HUB"  }}'
Example Response
{  "status": "done",  "output": {    "outcome": "added",    "pipelineAddId": "string",    "applicationId": "string"  },  "replay": {    "outcome": "added",    "pipelineAddId": "string",    "applicationId": "string"  },  "actionId": "string"}