Get chat

Returns the current state and complete message history of a chat. The response uses the same detail format as Get conversation .

GET https://api.platica.mx/v1/chat/{id}

URL parameters

ParameterTypeDescriptionRequired
idstringUnique chat ID returned when creating or listing chats.

Response

{
  "id": "conversation_doc_01JCHAT",
  "conversationId": "chat_01JCHAT23456789",
  "clientId": "client_123",
  "agentId": "agent_01JABCDEF23456789",
  "canSendDirectMessage": true,
  "workspaceId": "ws_001",
  "channelId": "workspace-ws_001-agent-agent_01JABCDEF23456789",
  "contactName": "Ana López",
  "phoneNumber": "5215512345678",
  "topic": "Plan selection",
  "platform": "platica",
  "source": "api_chat",
  "status": "active",
  "operation": "automatic",
  "messageCount": 2,
  "owners": ["sales@example.com"],
  "tags": ["prospect"],
  "creationDate": "2026-07-20T18:00:00.000Z",
  "lastUpdate": "2026-07-20T18:30:00.000Z",
  "messages": [
    {
      "id": "msg_user_01JCHAT98765432",
      "role": "user",
      "content": "Help me choose the right plan for my team.",
      "contentType": "text",
      "direction": "incoming",
      "status": "received",
      "creationDate": "2026-07-20T18:29:40.000Z"
    },
    {
      "id": "msg_assistant_01JCHAT98765433",
      "role": "assistant",
      "content": "For a team of 25 people using WhatsApp, these are the best options...",
      "contentType": "text",
      "direction": "outgoing",
      "status": "delivered",
      "creationDate": "2026-07-20T18:30:00.000Z"
    }
  ]
}
FieldDescription
idUnique, canonical document ID
conversationIdThread ID (chat_*). It does not identify the client
clientIdClient the chat is attributed to
agentIdPrincipal agent; temporary delegation to a subagent does not change it
canSendDirectMessageAlways true for internal Platica chats
workspaceIdAuthorized workspace ID
channelIdInternal channel ID
contactNameContact/customer name
phoneNumberCustomer phone number, when available
topicChat topic or subject
platformPlatform; platica for these chats
sourceAlways api_chat
statusChat status: active, finished, or expired
operationOperation mode
messageCountStored thread count
ownersList of responsible-user emails
tagsAssociated tags
creationDateCreation date in ISO 8601 format
lastUpdateLast update date in ISO 8601 format
messagesFull chat message history, in chronological order
FieldDescription
idUnique identifier of the message
roleSender role: user (customer) or assistant (agent/AI)
contentMessage content
contentTypeContent type: text, image, audio, etc.
directionDirection of the message: incoming or outgoing
statusMessage status: received, delivered, read, failed
creationDateMessage creation date and time