Resolve an unconfirmed chat publication
POST
/api/chat-endpoints/{endpointId}/publications/{publicationId}/resolvePersonal API keyConsole session
Resolve an unconfirmed chat publication.
After checking the provider conversation, an operator may mark an ambiguous publication delivered, retry it while accepting duplicate risk, or cancel it. Every resolution is audited.
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.
publicationIdstring (uuid)RequiredThe publication's id.
Request body
application/json · required
actionstringRequired
one of: "mark_delivered", "retry_anyway", "cancel"fileTransferobjectOptional
fileTransfer.phasestringRequired
one of: "consent_pending", "consent_sending", "consent_unknown", "awaiting_consent", "upload_pending", "uploading", "upload_unknown", "file_info_pending", "file_info_sending", "file_info_unknown", "delivered", "declined", "expired", "cancelled", "conflict"fileTransfer.versionintegerRequired
> 0≤ 9007199254740991Responses
204No contentDone; there is no body.
400Bad requestThe request is malformed or failed validation.
details names each field that failed.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).
Errors return {"error": "..."}, often with a code and details. See errors and limits.