Publish a Veyra Intelligence task comment to an external conversation

POST/api/chat-endpoints/{endpointId}/conversations/{conversationId}/publications
Personal API keyConsole session
Veyra Docs TeamUpdated Version 3 · History

Publish a Veyra Intelligence task comment to an external conversation.

Explicitly projects an eligible comment from the bound Veyra Intelligence task into the provider conversation. The endpoint, conversation, and comment must belong to the same binding. A Board send with an already-bound attachment returns 409 with code chat_board_send_attachments_already_bound and request-scoped details (endpointId, conversationId, idempotencyKey, attachmentIds). This durable rejection queues no publication and is replayed for the same key even if the file later becomes unbound. Correcting it requires an explicit new send identity. Other errors do not establish non-delivery.

Idempotency. Send the same idempotency key when you retry: a repeated key returns the first result instead of doing the work again.

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.
conversationIdstring (uuid)RequiredThe conversation's id.

Request body

application/json · required

commentIdstring (uuid)Optional
bodystringOptional
idempotencyKeystringOptional16–200 characters
attachmentIdsarray<string (uuid)>Optional

Responses

201SuccessCreated; the body holds the new resource.
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).
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