Undo a Nudge
Call back a Nudge before it goes, by the notificationId pipeline.nudge or outreach.send returned, until its undoUntil. After that it has been sent and can't be undone.
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.undoNudge' \ -H 'Content-Type: application/json' \ -d '{ "input": { "applicationId": "string", "notificationId": "string" }}'{ "status": "done", "output": { "outcome": "undone" }, "actionId": "string"}Pipeline situations POST
Each undecided candidate on a Job with the facts that decide whether to act: UMatch fit against the Job's floor, how they engaged, their Decision path and its track, momentum against the Job, whether the Job still needs people, and nudges sent. `allowed` is what an agent may do for them now, already filtered by the nudge limits; fast-track candidates come first. Without `jobId`, every open Job you can see, one Job a page.
Read signals POST
What happened since your cursor on the Jobs you can see: contact, email delivery, progress, share and sourcing events, oldest first. Poll with the returned cursor.