> ## Documentation Index > Fetch the complete documentation index at: https://docs.conduit.ai/llms.txt > Use this file to discover all available pages before exploring further. # Send Ticket Message > Send a new message within an existing ticket thread. ## OpenAPI ````yaml POST /v1/tickets/{id}/messages openapi: 3.0.0 info: title: Conduit API version: 1.0.0 description: Public API for Conduit. servers: - url: https://api.conduit.ai description: Production security: [] tags: - name: meta description: Discovery and API metadata endpoints. - name: agents description: >- V2 chat agent configuration, including instructions, skills, triggers, and automation behavior. - name: contacts description: >- Contact profile and contact-scoped related resources such as tickets and calls. - name: workspaces description: Workspaces accessible to the current API token. - name: escalations description: >- Chat escalations that require operator review, including message, proposed response, and disposition context when available. - name: conversations description: >- Canonical message threads. Use these endpoints to list threads, inspect conversation state, read transcripts, and send replies. - name: conversation-tags description: >- Conversation labels, root topics, and subtopics used for classification and topic analytics. - name: tickets description: >- Operational queue items tied to conversations, including ticket-scoped transcripts and replies. - name: calls description: Phone call records, transcripts, summaries, and recordings when available. - name: reservations description: >- PMS reservations synced from the workspace's integrations (Hostaway, Guesty, Airbnb, etc.), including guest identity, payment status, and stay dates. - name: appointments description: >- Scheduled appointments (bookings) backed by the Conduit booking service. Exposes allocation context and the upstream booking-service `external_id`. - name: helpdesk_tickets description: >- Helpdesk tickets mirrored from external helpdesk integrations (Zendesk, Pylon, Plain), including requester identity and upstream metadata. - name: kb description: >- Knowledge base search and node management. Nodes represent knowledge base entries (files or directories), chunks are the indexed retrieval units used by search. - name: skills description: >- Workspace agent skills that can be attached to V2 chat agents. Sidebar/global-assistant skills are intentionally excluded. - name: custom_tools description: >- Custom code tools: user-authored Python/JavaScript functions executed in a sandbox when an agent calls them. Includes a runtimes endpoint describing the entrypoint signature, return shape, and available dependencies per language. - name: inbox_types description: >- Workspace inbox types. Each id is stable and usable as a message trigger's `inboxTypeId` and as the `inbox_type_id` filter on list conversations. paths: /v1/tickets/{id}/messages: post: tags: - tickets summary: Send message to ticket description: >- Sends a reply within the ticket's current active thread. Requires a token with write access. operationId: sendTicketMessage parameters: - schema: type: string description: Ticket id. example: xd88mkfbmxgckpeyzs8m9r9d3d843me3 required: true name: id in: path - schema: type: string description: >- Optional workspace override. If omitted, Conduit resolves the ticket's workspace automatically. example: j57demo8f8x7c9v0n2q4r6t8y1u3i5o required: false name: workspace_id in: query requestBody: required: true content: application/json: schema: type: object properties: body: type: string attachments: type: array items: type: object properties: attachment_id: type: string minLength: 1 description: >- Convex storage id returned by the signed upload PUT response. This is the attachment id used by message and note APIs. name: type: string minLength: 1 description: Original filename to display. content_type: type: string minLength: 1 description: MIME content type supplied when the file was uploaded. content_length: type: integer minimum: 0 description: File size in bytes. required: - attachment_id - name - content_type - content_length description: >- Uploaded attachment metadata. First call `POST /v1/attachments/upload-url`, PUT the bytes to `upload_url`, then pass the PUT response `storageId` as `attachment_id`. Email delivers attachments directly. SMS and WhatsApp delivery depends on the configured Twilio/Linq sender and carrier media support; unsupported channels reject attachments. example: attachment_id: kg2a8d8w8zv1m9q9f9h7e3b2n97j6x2c name: failed-contacts.csv content_type: text/csv content_length: 18432 maxItems: 10 description: >- Request body for sending a message into an existing ticket thread. Attachments are uploaded first via `POST /v1/attachments/upload-url`; pass the PUT response `storageId` as `attachment_id`. Email supports file attachments. SMS and WhatsApp can deliver media only when the configured sender/provider supports the file type and size. example: body: Hi there, can you confirm check-in time? attachments: - attachment_id: kg2a8d8w8zv1m9q9f9h7e3b2n97j6x2c name: failed-contacts.csv content_type: text/csv content_length: 18432 responses: '201': description: Ticket message sent content: application/json: schema: type: object properties: data: type: object properties: id: type: string nullable: true workspace_id: type: string conversation_id: type: string ticket_id: type: string nullable: true channel: type: string nullable: true status: type: string enum: - sent required: - id - workspace_id - conversation_id - channel - status required: - data description: Result returned after a message is accepted for delivery. example: data: id: yh7t5azsr0zpfpyf67vtce0j6n844y1e workspace_id: j57demo8f8x7c9v0n2q4r6t8y1u3i5o conversation_id: ph77c0dy0mgdpzmqz6tesry8w184002s ticket_id: null channel: unthreaded_email status: sent '400': description: Invalid request content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '401': description: Unauthorized content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '403': description: Forbidden content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '404': description: Not found content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '409': description: Ticket cannot be replied to content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '429': description: Rate limit exceeded content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id security: - bearerAuth: [] components: securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: API Token description: >- Conduit API token. Use `Authorization: Bearer `. Read/write endpoints require a token with write access. ````