Hand a candidate back to Autopilot
End the hold-off on a person you acted on by hand, so the agent that owns them works them again. Name the Application or the person key.
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/autopilot.release' \ -H 'Content-Type: application/json' \ -d '{ "input": { "jobId": "string" }}'{ "status": "done", "output": { "owner": { "kind": "agent", "agent": "string" } }, "actionId": "string"}Who works each candidate POST
For every person on a Job: the working agent that owns them, the person who holds them (they acted by hand, so Autopilot leaves them alone until they hand them back or the hold-off ends), or nobody once they are closed.
Whether Autopilot works here POST
For the organization, a Client or a Job: whether Invyte's agents are enrolled, each stage on or off and where that comes from (the Job, its Client or the organization), each stage's preset (suggest, ask or act), whether agents are stopped (kill switch, staff stop, pause or budget), and whether you may change it.