Every Notivo request is authenticated with an API key. Give each application its own key and keep it on your server.
# Option A: API key header
curl https://api.notivo.link/api/session/status \
-H "x-api-key: YOUR_API_KEY"
# Option B: Bearer token
curl https://api.notivo.link/api/session/status \
-H "Authorization: Bearer YOUR_API_KEY"
Notivo authenticates each request with an API key. You send the key in the x-api-key header or as a Bearer token in the Authorization header. A key is linked to one WhatsApp session, so an application can only send through the session its key belongs to.
Use a separate key for each application so a website, an ERP and a script stay independent.
A key works with the session it belongs to, and the session ID in a request must match it.
Send the key as x-api-key or as a standard Bearer token, whichever your client prefers.
Standard 401 and 403 responses tell you whether a key is invalid or access is denied.
Access depends on three things: the key itself, the permissions that belong to it, and the session it is linked to. If a request fails with 403, check the key's permissions, your account status, and whether the session in the request belongs to that key.
No. The API key proves who is calling Notivo. The HMAC signature on a webhook proves that Notivo is the one calling you. Use both: authenticate outgoing requests with your key and verify incoming webhooks with your signature secret.
Give your online store and your accounting system different keys.
Use one key per client project and keep client integrations apart.
Separate your development key from the key used in production.
Run scheduled scripts with their own key and keep the credentials on the server.
See how this feature works with the rest of the platform, or browse all Notivo features.
Send messages with one REST endpoint and receive customer replies on your own webhook URL, signed so you can verify each request.
Read about Messaging APIConnect more than one WhatsApp number and manage every session, each with its own API key, from a single dashboard.
Read about Multiple sessionsConnect your ERP, CRM, WooCommerce store or custom software to WhatsApp through plain HTTP requests and webhooks.
Read about IntegrationsSign in to the Notivo dashboard and open your session. The API key is shown there.
Either works. Use x-api-key or the Authorization: Bearer header, whichever fits your HTTP client.
No. Anyone who opens the page could copy it. Call the API from your backend instead.
A 401 means the key is missing or invalid. A 403 means access is denied, for example because of the key's permissions or a session that does not belong to it.
Create your session, scan the QR code and send your first WhatsApp message through the Notivo API.
Get started Read the API documentation