Get conversation
Returns the current state and message history of a specific conversation.
GET https://api.platica.mx/v1/conversations/{id} URL parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
id | string | Unique identifier of the conversation: the id field returned by the listings. See How IDs work | ✓ |
Legacy lookup (deprecated)
Advertencia
For backward compatibility, the endpoint still accepts the customer's phone number or the conversationId as a fallback instead of the unique id. This behavior is deprecated: it can return several conversations and requires the channelId query parameter to disambiguate when multiple threads share the same conversationId. To query every conversation of a client use GET /v1/clients/{clientId}/conversations ; for a specific thread, always use its unique id.
| Query parameter | Type | Description | Required |
|---|---|---|---|
channelId | string | Only applies to the legacy lookup: narrows by channel when multiple conversations share the same conversationId | — |
Response
{
"workspaces": [
{
"id": "ws_001",
"name": "Soporte General",
"conversationsCount": 1,
"conversations": [
{
"id": "conv_001",
"conversationId": "987654321098",
"clientId": "client_123",
"agentId": "agent_001",
"source": null,
"canSendDirectMessage": true,
"workspaceId": "ws_001",
"channelId": "channel_001",
"contactName": "Juan Pérez",
"phoneNumber": "1234567890",
"topic": "Consulta General",
"platform": "whatsapp",
"owners": [
"soporte@empresa.com"
],
"tags": [
"prioridad-alta"
],
"creationDate": "2025-03-15T10:00:00Z",
"lastUpdate": "2025-03-15T10:15:00Z",
"status": "active",
"operation": "assistance",
"messageCount": 4,
"messages": [
{
"content": "Hola, necesito información sobre sus servicios.",
"contentType": "text",
"creationDate": "2025-03-15T09:58:00Z",
"direction": "incoming",
"files": [],
"id": "msg_001",
"images": [],
"owner": {
"id": "user_001"
},
"lastUpdate": "2025-03-15T09:58:00Z",
"role": "user",
"status": "received"
},
{
"content": "Hola, ¿cómo puedo ayudarte hoy?",
"contentType": "text",
"creationDate": "2025-03-15T10:00:00Z",
"direction": "outgoing",
"files": [],
"id": "msg_002",
"images": [],
"owner": {
"id": "agent_001"
},
"lastUpdate": "2025-03-15T10:00:00Z",
"role": "assistant",
"status": "delivered"
},
{
"content": "Tengo una duda sobre el producto que compré.",
"contentType": "text",
"creationDate": "2025-03-15T10:05:00Z",
"direction": "incoming",
"files": [],
"id": "msg_003",
"images": [],
"owner": {
"id": "user_001"
},
"lastUpdate": "2025-03-15T10:05:00Z",
"role": "user",
"status": "received"
},
{
"content": "Gracias por tu consulta. Te ayudaré con eso.",
"contentType": "text",
"creationDate": "2025-03-15T10:10:00Z",
"direction": "outgoing",
"files": [],
"id": "msg_004",
"images": [],
"owner": {
"id": "agent_001"
},
"lastUpdate": "2025-03-15T10:10:00Z",
"role": "assistant",
"status": "delivered"
}
]
}
]
}
]
} | Field | Description |
|---|---|
id | Unique, canonical document ID of the conversation. Use it in GET and PATCH /v1/conversations/{id} |
conversationId | Chat thread ID. It uses the chat_* format in the Chat API and does not identify the client |
clientId | ID of the client attributed to the conversation |
agentId | Principal agent ID; temporary delegation to a subagent does not change it |
source | Internal origin when available (for example api_chat); may be null for legacy conversations |
canSendDirectMessage | Can only be false on WhatsApp, Instagram, and Messenger/Facebook; calculated from the latest user message. Always true for internal Platica chats |
workspaceId | ID of the workspace the conversation belongs to |
channelId | Communication channel ID |
contactName | Contact/customer name |
phoneNumber | Customer phone number |
topic | Conversation topic or subject |
platform | Messaging platform (whatsapp, instagram, facebook, email, platica, etc.) |
owners | List of responsible-user emails |
tags | Tags associated with the conversation |
status | Operational stage: initiated, active, finished, spam, or expired |
operation | Conversation operation mode |
messageCount | Stored thread count; may include internal events not visible in messages |
messages | Normalized history available to the integration |
creationDate | Creation date in ISO 8601 format |
lastUpdate | Last update date in ISO 8601 format |
| Field | Description |
|---|---|
id | Unique identifier of the message |
content | Message content |
contentType | Content type: text, image, audio, etc. |
creationDate | Message creation date and time |
direction | Direction of the message: incoming or outgoing |
files | List of files attached to the message |
images | List of images attached to the message |
lastUpdate | Date the message was last updated |
owner | Object with minimal sender information. Currently includes id when available |
role | Sender role: user (customer) or assistant (agent/AI) |
status | Message status: received, delivered, read, failed |
Consejo
If you need to change owners or status, use the update conversation endpoint.