Skip to Content
InvyteDocs

Follow-ups due with Clients

The follow-ups due now on candidates waiting on Clients, one per Job and kind, in order. Computed from when each candidate was sent, so a missed check loses nothing.

POST
/operations/delivery.dueFollowUps

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/delivery.dueFollowUps' \  -H 'Content-Type: application/json' \  -d '{  "input": {}}'
Example Response
{  "status": "done",  "output": {    "due": [      {        "jobId": "string",        "clientId": "string",        "deliveryId": "string",        "kind": "reminder_24h",        "dueAt": "2019-08-24T14:15:22Z",        "applicationIds": [          "string"        ]      }    ]  },  "actionId": "string"}