# How do EnableCalls API keys work?

Every request is authenticated with a key you create in the dashboard. Keep keys on your server or in your automation tool's credential store.

## How do I send my key?

```http
Authorization: Bearer ec_live_…
```

Keys start with `ec_live_` and end with a checksum, so a mistyped key is refused at once and secret scanners can spot one pushed to a repository.

## How do I create, scope and revoke keys?

- Only the workspace owner can create or revoke keys, on **Developers** in the dashboard. Each create and revoke appears in your notifications.
- A key is shown once, when it is created. We keep only a fingerprint, so a lost key cannot be shown again: create a new one.
- Up to 10 active keys per workspace. You can give a key an expiry date.
- Use one key per integration, so you can revoke one without touching the others. Revoking takes effect immediately.

| Access | Can |
| --- | --- |
| Full access | Everything: place and cancel calls, run campaigns, manage contacts, do-not-call and webhooks. Creating one records your confirmation that the people you call agreed to hear from you. |
| Read only | Read employees, numbers, coins, calls, leads, campaigns, contacts, appointments, do-not-call, webhooks and events. Any write answers `403 insufficient_scope`. |

## Can I call the API from a web page?

No. A key in a web page or mobile app can be copied by anyone, so requests sent from a browser are refused with `403 browser_requests_not_allowed`. Call the API from your server or automation tool.

## What do authentication errors mean?

| Status | code | Meaning |
| --- | --- | --- |
| 401 | `missing_api_key` | No `Authorization: Bearer` header. |
| 401 | `invalid_api_key` | Not a key we know (mistyped or deleted). |
| 401 | `api_key_revoked` | The key was revoked. |
| 401 | `api_key_expired` | The key passed the expiry chosen when it was created. |
| 403 | `account_inactive` | The workspace is suspended or closed. |
| 403 | `insufficient_scope` | A read-only key was used for a write. |
| 403 | `browser_requests_not_allowed` | The request came from a web page. |

## More EnableCalls API docs

- [Overview](https://enablecalls.com/developers.md): Place AI phone calls, run calling campaigns and get every conversation's outcome, summary and transcript from your CRM, website, n8n, Make or Zapier.
- [Calls and retries](https://enablecalls.com/developers/calls.md): How EnableCalls API calls move from queued to completed: calling hours, do-not-call, coins, the 30-minute cooldown, automatic retries for unanswered calls and every status.
- [Webhooks and events](https://enablecalls.com/developers/webhooks.md): Receive call.completed, call.not_connected, lead and appointment events on your URL, verify the HMAC-SHA256 signature, and understand retries and the event log.
- [Errors and limits](https://enablecalls.com/developers/errors.md): The EnableCalls API error format, rate limits per key, Idempotency-Key for safe retries, dry runs and starting_after pagination.
- [n8n, Make, Zapier](https://enablecalls.com/developers/no-code.md): Call new leads from n8n, Make, Zapier or Pabbly Connect with an HTTP request to the EnableCalls API, and receive call results with a webhook trigger.
- [API reference](https://enablecalls.com/developers/reference.md): Every EnableCalls API endpoint: calls, leads, campaigns, contacts, appointments, do-not-call, webhooks, events, employees and phone numbers, with parameters and fields.

Canonical page: https://enablecalls.com/developers/authentication
