A conversation is the WhatsApp thread between your business and a contact. Almost every send and action endpoint (Documentation Index
Fetch the complete documentation index at: https://docs.1to1ai.com/llms.txt
Use this file to discover all available pages before exploring further.
/conversation/*) takes it in the
request body under the conversation object.
Identifying a conversation
Theconversation object accepts one of three identifiers. The resolver
prioritizes them in this order: uuid → whatsapp_user_id → phone.
The UUID from a
GET /conversations. The most direct and stable path.The contact’s identifier in Meta. Recommended for new clients — it
survives the migration to BSUID.
Number in E.164 format (
+5215512345678). Normalized to digits before the
lookup. Useful when all you have is the phone.phone and whatsapp_user_id point to the same value today. They coexist for
Meta’s transition to alphanumeric identifiers (BSUID). If you’re starting from
scratch, store whatsapp_user_id.The 24h window
This is WhatsApp’s core concept and it decides what you can send.The contact messages you
WhatsApp opens a 24-hour window. Each new message from the contact
resets the timer.
Checking the window status
Before sending a free-form message, you can verify whether the window is open withPOST /conversation/status:
window.status (open or closed) and
window.hours_remaining, plus the assignment, mailbox, tags, and
inbox_status of the conversation. Use it to decide between a free-form
message and a template.
Next steps
Send messages
Text, media, quick replies, and templates.
Templates
How to send templates when the 24h window is closed.