Authentication
Every request carries an API key in the Authorization header.
Authorization: Bearer np_live_...Creating keys
Create, name and revoke keys under Developers in your dashboard. A key is shown once when it is created. We keep only a hash of it, so it cannot be shown again: make a new one if you lose it. An account can have up to 10 active keys. Revoking a key takes effect at once.
Full access and read-only
| Full access | Everything: read, place calls, run campaigns, change leads and the do-not-call list. |
|---|---|
| Read only | Every GET endpoint. Anything else returns 403 insufficient_scope. Use it for dashboards and reports so they can never place a call by mistake. |
Keeping keys safe
- Keep a key on your server or in your automation tool’s credential store. Never put it in a web page or a mobile app: anyone could copy it.
- Use one key per system, so you can revoke one without touching the others.
- Keys start with
np_live_, so a secret scanner can spot one pushed to a repository.
Errors
A missing, wrong or revoked key returns 401 unauthorized. A switched-off account returns 403 forbidden. See Errors and limits.
Last updated 13 November 2026. Found something wrong on this page? Email bodavulasiddardha@navaprastha.in and we will correct it.