What it is
YCloud delivers inbound WhatsApp messages to your webhook endpoint. After you accept an event, you can mark the message as read or show a temporary typing indicator while your application prepares a reply.Before you begin
- Configure a webhook endpoint for
whatsapp.inbound_message.received. - Validate the
YCloud-Signatureheader before processing events. - Store the inbound message
id. - Connect the business phone number that received the message.
How it works
- Receive and authenticate the webhook event.
- Deduplicate the event by event
id. - Extract the inbound message
idand content. - Optionally mark the message as read.
- Show a typing indicator only when a reply is being prepared.
- Send the reply with the WhatsApp Messages API.
Request
Mark a message as read
POST /whatsapp/inboundMessages/{id}/markAsRead
Show a typing indicator
POST /whatsapp/inboundMessages/{id}/typing
Response
A successful request returns HTTP200 with no response body.
Processing guidance
- Acknowledge the webhook before starting slow AI or business processing.
- Preserve message order per conversation where your use case depends on it.
- Handle every supported inbound
typeexplicitly and retain unsupported payloads for investigation. - Use the message context when replying to a specific inbound message.
Limits and troubleshooting
- Do not show a typing indicator unless a response will follow.
- Use the inbound message ID, not the webhook event ID, in the action path.
- Make webhook handling idempotent because delivery can be retried.
- If an action fails, log the YCloud
requestIdwithout logging message contents or credentials.
Inbound payload examples
Inspect text, media, interactive, commerce, and system message payloads.
Mark as read API
Inspect the complete endpoint contract.

