Refresh a sourcing run
Check a running External discovery search with the partner now instead of at its next scheduled check, as Refresh on the Sourcing tab does. A finished run is returned as it is.
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/sourcing.refreshRun' \ -H 'Content-Type: application/json' \ -d '{ "input": { "jobId": "string", "runId": "string" }}'{ "status": "done", "output": { "runId": "string", "status": "QUEUED" }, "actionId": "string"}List sourcing runs POST
A Job's External discovery runs, newest first, with how many people each found: 20 a page by default, older ones through `nextCursor`.
Save a Job's External discovery settings POST
Set what External discovery partners look for on a Job (up to five criteria, each required or nice to have) and which contact details they look up, and turn External discovery on. Saving starts no search now: on a published Job start one with sourcing.start; on a draft Job, publishing it (jobs.publish) starts one paid search within the daily sourcing budget. Other channels keep their setting.