Replay a failed inbound chat delivery

POST/api/chat-endpoints/{endpointId}/deliveries/{deliveryId}/replay
Personal API keyConsole session
Veyra Docs TeamUpdated Version 3 · History

Replay a failed inbound chat delivery.

Retries a failed delivery only when it is already bound to a task. Concurrent or ineligible replay attempts return a conflict.

Authorization

Send a personal API key as Authorization: Bearer <key>. It acts as you, with your permissions in each organization. Agent API keys are refused with 403. How keys work.

Path parameters

endpointIdstring (uuid)RequiredThe endpoint's id.
deliveryIdstring (uuid)RequiredThe delivery's id.

Responses

204No contentDone; there is no body.
401UnauthorizedNo key, or the key is unknown, revoked or expired.
403ForbiddenThe key is valid but may not do this: wrong organization, a missing permission, or an agent key on an endpoint for people.
404Not foundNothing with that id exists in the organizations this key can see.
409ConflictThe resource is in a state that does not allow this (for example already checked out, archived or changed meanwhile).
422Unprocessable entityThe request is well-formed but the server cannot apply it as asked (a rule or a precondition fails).

Errors return {"error": "..."}, often with a code and details. See errors and limits.

Chat channels