Read effective limits
agent_identity_id to select an agent when authenticating with an organization-wide credential. The response contains agent_identity_id, effective limits, and available usage counters. Dictionary keys retain their whatsapp. prefix. The daily usage counter counts outgoing messages, including replies, in the agent’s rolling 24-hour window.
Independent safeguards
Group sends count toward the daily message allowance, consecutive-unanswered limit, and distinct-conversation limit alongside direct messages. An allowed incoming message from another participant in the current connection resets that group’s unanswered count. First-contact and follow-up limits apply only to direct conversations. The API exposes limits for daily messages, direct first-contact outreach, unanswered messages, follow-ups, distinct conversations, minimum spacing, and text/media sizes. In a direct conversation, before that recipient’s first WhatsApp reply, the initial policy allows up to three opening messages of at most 159 Unicode code points each. Links, phone numbers, media, and email addresses are not allowed in those messages by default. Four independent settings control those content permissions separately from the opening-message count and length.
The initial daily allowance is 1,000 outgoing messages per agent in a rolling 24-hour window, including replies. This allowance remains configurable. Read the limits endpoint for your agent’s effective values instead of inferring them from this fallback table. Access approval remains separate from these limits.
A policy rejection is not permission to switch identities or channels, split a message, create a new logical-send key, or automatically retry. Follow the response’s error and retry guidance, and inspect the original logical send if acceptance is uncertain.