Update conversation status
Archive or activate a conversation. Requires accountId in request body.
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
The conversation ID (id field from list conversations endpoint). This is the platform-specific conversation identifier, not an internal database ID.
Social account ID
"active" | "archived"Response Body
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.messages.updateInboxConversation({ path: { conversationId: 'conversation_abc123', }, body: { accountId: 'account_abc123', status: 'active', },});console.log(data);{
"success": true,
"data": {
"id": "string",
"accountId": "string",
"status": "active",
"platform": "string",
"updatedAt": "2019-08-24T14:15:22Z"
}
}{
"error": "Unauthorized"
}Get conversation GET
Retrieve details and metadata for a specific conversation. Requires accountId query parameter.
Mark a conversation as read POST
Marks all unread incoming messages in the conversation as read. For WhatsApp, this also sends read receipts (blue ticks) to the contact, EXCEPT on coexistence accounts (where the WhatsApp Business app on the customer's phone owns read state and we never override it). This is the explicit, human-driven counterpart to `GET .../messages`, which is side-effect-free and does NOT mark anything read. Call this when a user actually views the conversation.