How do I generate API keys?
Open the Whats91 customer dashboard, go to Developer API Tokens, and create or copy a public API token for server-side use.
Generate and manage managed w91_live_ API tokens from the Whats91 dashboard.
Use this page to understand where public API keys are generated, how they should be stored, and how they are used with v3 endpoints.
Create managed tokens from Developer -> API Tokens in the Whats91 customer dashboard. New documentation should recommend managed w91_live_ tokens instead of legacy customer tokens.
| Scope | Behavior |
|---|---|
| global | Token can resolve any allowed sender for the customer. |
| selected_number | Token is bound to the currently selected sender. |
| specific_number | Token is bound to a sender chosen from connected numbers. |
Warning
Managed tokens start with w91_live_. Whats91 stores only a SHA-256 hash, token prefix, and last four characters, along with scope, sender binding, expiry, last used time, revoked time, and status.
Open the Whats91 customer dashboard, go to Developer API Tokens, and create or copy a public API token for server-side use.
No. Keep public API tokens on trusted servers and never expose them in browser-side JavaScript or mobile app bundles.
Yes. Create a new token, update your server configuration, verify requests, and then disable the old token from the dashboard.