Pipeline activity
One Job's Application updates, newest first: moves, decisions, placements and status changes, with who made them. 20 a page by default; pass `next` as `cursor` for older ones.
bearerAuthorizationBearer <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.
Idempotency-Key?stringMakes a write safe to repeat: the same key and input return the first result. Required for agents' writes and for anything a person confirms.
^[A-Za-z0-9._:-]+$8 <= length <= 128application/json- body
input*confirmation?stringThe id from a confirm or awaiting_approval Outcome, sent with the same input and key to go ahead.
Done. A replay of the same key and input omits output.
application/json- response
status*unknownoutput?actionId*stringcurl -X POST 'https://www.invyte.ai/api/recruiter/v1/operations/pipeline.activity' \ -H 'Content-Type: application/json' \ -d '{ "input": { "jobId": "string" }}'{ "status": "done", "output": { "updates": [ { "id": "string", "applicationId": "string", "action": "string", "description": "string", "actorName": "string", "actorType": "string", "at": "2019-08-24T14:15:22Z", "fromStatus": "string", "toStatus": "string", "decisionRecordId": "string" } ], "next": "string" }, "actionId": "string"}Edit a note POST
Change a note's text or rating. Only its author, or an organization admin, may.
Add someone to a Job POST
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.