Mark inbound messages as read (blue ticks)

Sends a WhatsApp **read receipt** so the customer sees the blue ticks on the messages they sent you. Call this the moment one of your operators opens the conversation in your own UI. If your agents read WhatsApp inside your CRM, nobody ever opens the chat in WhatsApp — the customer's messages stay on double grey ticks and the conversation feels ignored. **Scope is `whatsapp.send`, not `whatsapp.read`:** marking read TRANSMITS a receipt from your number to the customer's device, so it is an outbound action. Any client that can already send can mark read — no new scope, no re-consent. Supply `connectionId` plus at least one of `phone` / `messageId`. `messageId` is WASync's stable id (a cuid) of an INCOMING message — not `waMessageId`. When both are given, `messageId` wins. Idempotent by nature: re-marking an already-read conversation is a no-op, so no `idempotencyKey` is accepted and no rate limit applies. Retry freely. Connection differences: WAPP/QR connections mark the whole chat; WABA (official API) connections can only mark one specific message, so a `phone`-only request resolves your most recent inbound message from that number automatically.

curl -X POST "https://example.com/messages/read" \  -H "Content-Type: application/json" \  -d '{    "connectionId": "conn_8f3a21",    "phone": "40700000000"  }'

{  "ok": true,  "marked": 3}