Invite a prospect to apply
Email a Sourcing prospect for this Job an invitation to apply. They apply like anyone else; nothing is shared or created until they do.
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?replay?actionId*stringcurl -X POST 'https://www.invyte.ai/api/recruiter/v1/operations/sourcing.invite' \ -H 'Content-Type: application/json' \ -d '{ "input": { "jobId": "string", "prospectContextLinkId": "string" }}'{ "status": "done", "output": { "invitationId": "string", "delivery": "sending", "expiresAt": "2019-08-24T14:15:22Z" }, "replay": { "invitationId": "string" }, "actionId": "string"}View a sourcing run POST
One External discovery run of a Job and the people it found: where they work, how well they matched, and whether they were invited or applied.
List a Job's prospects POST
Everyone a Job's sourcing found, across runs, and everyone added to it from Talent Hub (their `sourcingRunId` is null), newest first: where they work, how well they matched, and whether they were invited or applied. Each `id` is what `sourcing.setProspectStatus` takes, and each `personKey` what Talent Hub reads take.