EvolutionAPI
[API Issue] {{baseUrl}}/chat/whatsappNumbers/{{instance}} - Account Ban Risk When Checking Multiple Numbers
Welcome!
- [x] Yes, I have searched for similar issues on GitHub and found none.
What did you do?
Description
When checking multiple WhatsApp numbers using the endpoint {{baseUrl}}/chat/whatsappNumbers/{{instance}}, checking a lot of numbers can lead to the WhatsApp account being banned or flagged.
Problem
The endpoint does not implement proper rate limiting or account protection mechanisms when bulk checking WhatsApp numbers. This causes WhatsApp to detect suspicious activity and ban/restrict the account.
Steps to Reproduce
- Call the endpoint
{{baseUrl}}/chat/whatsappNumbers/{{instance}} - Make multiple requests checking a large number of WhatsApp accounts
- After checking many numbers, observe that the WhatsApp account gets banned or restricted
Expected Behavior
The endpoint should:
- Implement rate limiting to prevent account bans
- Add delays between requests to appear as normal user behavior
- Provide error handling and warnings when approaching account restriction thresholds
- Document best practices for bulk checking numbers safely
Actual Behavior
The WhatsApp account gets banned or restricted when checking a lot of numbers without any warnings or protection mechanisms.
Environment
- Evolution API version: 2.3
Additional Context
This is a critical issue as it can result in complete loss of the WhatsApp account. Proper safeguards and rate limiting are essential for this endpoint.
What did you expect?
The endpoint should safely handle bulk checks of multiple WhatsApp numbers without causing the account to be banned or restricted. The API should implement rate limiting, add delays between requests, and provide appropriate error handling to prevent account suspension.
After checking multiple numbers using the endpoint, the WhatsApp account gets banned or restricted without any prior warning or error message. This happens because the endpoint makes requests too quickly and WhatsApp detects it as suspicious activity.
No response
Which version of the API are you using?
v2.3.4 or later docker
