Edit message
Edit the text and/or reply markup of a previously sent Telegram message. Only supported for Telegram. Returns 400 for other platforms.
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
The conversation ID
The Telegram message ID to edit
Social account ID
New message text
New inline keyboard markup
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.editInboxMessage({ path: { conversationId: 'conversation_abc123', messageId: 'message_abc123', }, body: { accountId: 'account_abc123', },});console.log(data);{
"success": true,
"data": {
"messageId": 0
}
}{
"error": "Unauthorized"
}Add reaction POST
Add an emoji reaction to a message. Platform support: - Telegram: Supports a subset of Unicode emoji reactions - WhatsApp: Supports any standard emoji (one reaction per message per sender) - All others: Returns 400 (not supported)
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.