WhatsApp Daily Sending Limit & Multi-Device Number Blocking Issue

[BilalAhmed9898]

Hi Team,

I want to ask about the WhatsApp sending limit through this system. Currently, I am sending around 200 messages daily, but when using the multi-device setup, around 10 numbers got blocked.

Can you please confirm if it is safe to send up to 500 messages daily through this system on WhatsApp? Also, are there any recommended limits or best practices to avoid number blocking?

Please guide me on this.
Thanks.

[aldinokemal]

There is no limit on this side, and I cannot confirm any number as safe.

This project is an unofficial client on top of whatsmeow. A send request goes straight to WhatsApp with no queue, no throttle and no delay (src/usecase/send.go:57-58), so whatever you push through the API is exactly what WhatsApp sees. 200/day, 500/day, the blocking decision is made entirely on WhatsApp's side and nothing in this repo can influence it. Anyone quoting you a "safe" daily figure is guessing.

What actually drives the blocks is not the raw count, it is: sending to people who never messaged you first, recipients pressing Block/Report, identical message bodies to many numbers, and brand new or freshly relinked numbers being used at volume on day one.

If you hit error 463 the API surfaces it as a distinct error (src/usecase/send.go:118-126, src/pkg/error/whatsapp_error.go:93). That is WhatsApp's reach-out timelock on starting new chats. Treat it as a stop signal, not something to retry, since retrying it makes things worse.

Things you can do from your side:

• Pace the sends in your own caller. There is no built in rate limiter here, so you have to add the spacing yourself.
• Prefer recipients who opened the conversation with you.
• Vary message content instead of sending one identical template to everyone.
• Warm up a new number slowly over days rather than starting at full volume.
• Optionally send a typing indicator first via POST /send/chat-presence (src/ui/rest/send.go:27).

If you need guaranteed volume with an SLA, use the official WhatsApp Cloud API. This is stated in the readme as well (readme.md:735-736): the project is unofficial and not affiliated with WhatsApp, and bans are a risk you take on.

[BilalAhmed9898]

Hi, Thank you for taking the time to explain this in such detail. I really appreciate the clarification. I've actually been using this project for about a year now, and it's been the backbone of one of my production systems. Before the official multi-device/multi-client support was released, I had already modified the project to support multiple clients because I manage around 300 customer accounts. After spending time understanding the architecture, I changed it to use separate databases per client to fit my use case. Later, when you released the built-in multi-client feature with a shared database approach, I migrated over to that. Today I'm using the project in production as part of a much larger messaging platform. Around it I've built additional services using Kafka, Redis, scheduled workers, and other background services to reliably schedule and deliver messages for each client throughout the day. On average, the system processes around *10,000 messages daily*. I have to say, your last major update kept me busy for almost *three days* while I updated and tested everything... 😂 But that's part of the fun of maintaining a system built on an actively developed project. Thanks again for all the work you've put into this project. It's been incredibly valuable, and I really appreciate your continued maintenance and responsiveness to the community. Keep up the great work!

…

On Sat, Jul 25, 2026 at 8:05 AM Aldino Kemal ***@***.***> wrote: There is no limit on this side, and I cannot confirm any number as safe. This project is an unofficial client on top of whatsmeow. A send request goes straight to WhatsApp with no queue, no throttle and no delay ( src/usecase/send.go:57-58), so whatever you push through the API is exactly what WhatsApp sees. 200/day, 500/day, the blocking decision is made entirely on WhatsApp's side and nothing in this repo can influence it. Anyone quoting you a "safe" daily figure is guessing. What actually drives the blocks is not the raw count, it is: sending to people who never messaged you first, recipients pressing Block/Report, identical message bodies to many numbers, and brand new or freshly relinked numbers being used at volume on day one. If you hit error 463 the API surfaces it as a distinct error ( src/usecase/send.go:118-126, src/pkg/error/whatsapp_error.go:93). That is WhatsApp's reach-out timelock on starting new chats. Treat it as a stop signal, not something to retry, since retrying it makes things worse. Things you can do from your side: - Pace the sends in your own caller. There is no built in rate limiter here, so you have to add the spacing yourself. - Prefer recipients who opened the conversation with you. - Vary message content instead of sending one identical template to everyone. - Warm up a new number slowly over days rather than starting at full volume. - Optionally send a typing indicator first via POST /send/chat-presence (src/ui/rest/send.go:27). If you need guaranteed volume with an SLA, use the official WhatsApp Cloud API. This is stated in the readme as well (readme.md:735-736): the project is unofficial and not affiliated with WhatsApp, and bans are a risk you take on. — Reply to this email directly, view it on GitHub <#667?email_source=notifications&email_token=AXLOMNXNIJMIAL2IFUL5IFL5GQPWPA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXG42TAMBUUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-17775004>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXLOMNWUGH63CCI5NNQ5MPD5GQPWPAVCNFSNUABIKJSXA33TNF2G64TZHM2DKNZUGM2TEOJQHNCGS43DOVZXG2LPNY5TCMBQGE3TEMBQUF3AE> . You are receiving this because you authored the thread.Message ID: <aldinokemal/go-whatsapp-web-multidevice/repo-discussions/667/comments/17775004 @github.com>