Skip to Content
InvyteDocs
Autopilot & approvals

Who owns these candidates

Which working agent owns each person on a Job now (sourcing, communication, pipeline or delivery), worked out from where they stand, with any override a person or the orchestrator set, and whether a person holds them (ownedBy kind person: leave them alone). Ids and states only.

POST
/operations/owners.get

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?
actionId*string
Example Request
curl -X POST 'https://www.invyte.ai/api/recruiter/v1/operations/owners.get' \  -H 'Content-Type: application/json' \  -d '{  "input": {    "jobId": "string",    "subjects": [      "string"    ]  }}'
Example Response
{  "status": "done",  "output": {    "jobId": "string",    "owners": [      {        "subject": "string",        "owner": "sourcing",        "derived": "sourcing",        "state": {          "kind": "application",          "status": "SUBMITTED"        },        "override": {          "agentId": "sourcing",          "reason": "string",          "setAt": "2019-08-24T14:15:22Z",          "setBy": "string"        },        "ownedBy": {          "kind": "agent",          "agent": "string"        }      }    ]  },  "actionId": "string"}

An agent's success measures POST

How well one working agent did since a date, on the Jobs you can see: its actions joined to the replies, consents, applications, shortlistings, meetings and hires that followed them within each attribution window, as its success measure (sourcing: consent rate and UMatch; communication: reply, consent and unsubscribe rates; pipeline: completion rate and days; delivery: shortlist acceptance; orchestrator: days to shortlist and cost per shortlisted candidate; intake: time to open and requirements loosened later; workflow: designs delivered and drafts per design), with the trend against the window before.

Hand a candidate to another agent POST

Make one working agent own a person on a Job, whatever their stage says, until they close; agentId null hands them back to the default. The reason is kept with the override.