Closed laloyalo closed 3 years ago
@laloyalo Hi, did you manage to solve it?
Hello @origliante , I kinda solved it by implementing a service that authenticates the WA API and stores the token in the file system, so that it can be later configured in Prometheus. There's a much simpler solution, and that is to migrate to v2.29.3 of the WA containers, as they mention in the changelog page the v2.29.1 added support for the API key, so you may just update to v2.29.3 (the recommended update) and get this new feature, which was probably the case of me reading the documentation for the latest version and not the version I was actually running 😅.
I will be closing this, as this is actually implemented in v2.29.3, not v2.27.12. Thanks!
Hello, WhatsApp team. I am trying to follow the instructions described in the Stats and Metrics documentation to enable API key access to the
waweb
. I am running in K8s and have configured the env variable as described in the instructions. When I attempt to send a request using the API and the headers:Where
{{AdminAuthToken}}
is a 50 randomly generated characters string.The following error is returned by the API.
And the following logs appear in the
waweb
container.It looks like the role provided to the authenticated Apikey does not have the proper permissions to access the endpoints. Are there any missing steps to get this working?
Image and tag version:
docker.whatsapp.biz/web:v2.27.12
Thank you!