GOWA does not rate-limit requests. What limits do exist, how WhatsApp restricts senders, and how to pace your traffic.
GOWA has no rate limiter. It does not count requests, return 429 for request volume, or send X-RateLimit-* headers. Every request you make is passed to WhatsApp immediately. Pacing is your responsibility.
WhatsApp does not publish its limits for linked devices, and they change. Accounts that send too much, too fast, or to people who never wrote to them are restricted or banned. GOWA cannot detect or prevent this in advance.The one signal GOWA surfaces is WA_REACHOUT_TIMELOCK (HTTP 429):
WhatsApp returns this (server error 463) when the account is temporarily blocked from starting new chats. It cannot be bypassed or retried away. Until it lifts:
Only message people who have messaged you first, or reply in existing chats.
Sending one message from the phone itself sometimes clears it sooner.
If GOWA is reachable from the internet, add request limits at your reverse proxy, especially for failed Basic Auth logins and, with MCP OAuth, /oauth/authorize. For example, with nginx: