Update Conversation
Lets you update the owners and status of a conversation. The update applies only to the conversation identified by its unique id.
PATCH 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 | ✓ |
Advertencia
For backward compatibility, the endpoint still accepts the customer's phone number or the conversationId as a fallback. This behavior is deprecated: always use the unique id to update exactly the thread you intend to modify.
Request body
You must send at least one of the following fields:
| Field | Type | Description |
|---|---|---|
owners | array | List of responsible-user emails |
status | string | New conversation status |
Example
{
"owners": [
"soporte@empresa.com",
"ventas@empresa.com"
],
"status": "finished"
}Rules for owners
- Must be sent as email addresses
- Each email must exist as a workspace user
status transition rules
Allowed values: active, finished, spam, expired.
Expiring a conversation is a form of closing (isFinished): the final status can end up as finished or expired depending on whether the customer ever replied in the thread.
- External channels (WhatsApp, Instagram, Facebook):
expiredis a terminal state. The customer's next contact will start a new conversation. - Internal API chats: a closed or expired chat can be reopened, either with a
PATCHtostatus: "active"or automatically when it receives a new message through the Chat API .
Response
{
"status": "success",
"message": "Conversation updated successfully",
"data": {
"ids": [
"conv_001"
]
}
}