-
-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot check if a phone number is on whatsapp or not - METHOD NOT IMPLEMENTED BY THE ENGINE #37
Comments
Could you share the full response please? |
hi, so , yesterday it was giving me 500 how many number verifications/checks can I do before getting banned ? |
okay , after debugging I found the problem and the solution : The issue is that when a check_phone_number request is made before the webhooks are initialized on the server, it does not return a response. In other cases, the response contains an error stating that the server cannot read the properties of the WhatsApp service and is unable to retrieve the check_number. Upon further investigation, it was determined that when the check_phone_number request is made before the websockets are fully loaded on the server, it causes a freeze in the docker container, which prevents the server from being able to send messages afterwards. However, the server is still able to refresh the Swagger UI. To resolve this issue, it is recommended to ensure that the webhooks are fully initialized on the server before making the endpoints available for the , in order to avoid the freeze in the docker container. |
Hi! We've added contacts endpoints in WAHA Right now it supports:
It supports default engine, so no needs to use venom for phone number check. Please have a look, it may help you! The endpoints are available in WAHA Plus |
Great idea, thank you! We'll work on that #40 |
hi every time that I check if a phone number is on whatsapp I get a 422
I tried using both engines, but with VENOM , it's worse , it returns a 500
The text was updated successfully, but these errors were encountered: