The Get conversation message endpoint returns a single message from a conversation.

Requirements: Base URL, Authentication, Error codes

Scope: messaging.conversations.read

What this does

When you send a Get conversation message request with a conversation ID and message ID,

When to use it

• Retrieve a specific message after listing messages with Get list of conversation messages
• Fetch message content and delivery status for troubleshooting
• Link directly to a single message from an external system

Endpoint

GET /api/v4/messaging/conversations/{conversation_id}/messages/{message_id}

Request parameters

Path parameters

• conversation_id
  The unique identifier of the conversation (UUID).
• message_id
  The unique identifier of the message (UUID).

Examples

Minimal request

curl -X GET "https://{cluster_id}.voiso.com/api/v4/messaging/conversations/0b62763c-40d6-4ec8-8380-3cb94e442a75/messages/1f839685-9b8f-4d01-8a7a-c5a91532e2f7" \
  -H "Authorization: Bearer <contact_center_api_key>" \
  -H "Content-Type: application/json"

Response

If successful, the API returns a message object.

{
  "message": {
    "id": "1f839685-9b8f-4d01-8a7a-c5a91532e2f7",
    "conversation": {
      "id": "0b62763c-40d6-4ec8-8380-3cb94e442a75"
    },
    "direction": "outbound",
    "user": {
      "id": "0b97ce11-b6e0-49b4-8f92-68040aa324bf",
      "name": "Jane Doe",
      "email": "[email protected]"
    },
    "target_user": null,
    "content_type": "text",
    "content_data": {
      "text": "Hi, how can I help you?"
    },
    "status": "delivered",
    "status_reason": null,
    "created_at": "2025-11-11T12:00:00.216Z",
    "updated_at": "2025-11-11T12:00:00.216Z"
  }
}

Notes

• content_data depends on content_type:

  • For text, content_data includes text.
  • For audio, document, image, video, or voice, content_data can include url, plus optional filename, size, and caption.

• user can be null for inbound contact messages or system generated messages.

• target_user is used for whisper messages and can be null.

Troubleshooting

401 Unauthorized

What to check:

• You are sending Authorization: Bearer <contact_center_api_key>.
• Your Base URL includes the correct {cluster_id}.

403 Forbidden

What to check:

• The API key is valid, but does not have access to this conversation or message.

404 Not found

This usually means the conversation ID or message ID does not exist, or you do not have access to it.

What to check:

• Confirm the conversation ID using Get list of conversations.
• Confirm the message ID using Get list of conversation messages.

Example response:

{ "error": "Not found" }

429 Too many requests

What to do:

• Reduce request frequency and retry with backoff.