Withdraw a candidate without changing an existing qualified serving route
const url = 'https://api.vocapable.com/v1/agents/example/receptionist-release/candidate/withdraw';const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.vocapable.com/v1/agents/example/receptionist-release/candidate/withdraw \ --header 'Authorization: Bearer <token>'Close the candidate and return its line to unrouted.
The immutable candidate version stays in history; only the ledger row closes. The line is cleared only while it still routes directly to this agent and the agent is still unqualified, so a withdrawal can never clear a route that answers with a qualified version. Clearing, like the routing PATCH, needs no carrier and no production key.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Header Parameters
Section titled “Header Parameters”Responses
Section titled “Responses”Successful Response
One staged candidate and its lifecycle.
While status is staged the line routes directly to the agent, whose active
version is this unqualified candidate: carrier ingress answers only a challenge-verified
carrier canary with it and gives every other caller the deterministic fallback. The
candidate closes as qualified when the matching qualified version is published,
withdrawn when its route is removed, or superseded by a restaged candidate.
object
Example
{ "status": "staged"}Validation Error
object
object
object
Examplegenerated
{ "detail": [ { "loc": [ "example" ], "msg": "example", "type": "example", "input": "example", "ctx": {} } ]}