> ## Documentation Index
> Fetch the complete documentation index at: https://support.configview.com/llms.txt
> Use this file to discover all available pages before exploring further.

# ElevenLabs setup

ConfigView reads your ElevenLabs (voice AI) workspace through the ElevenLabs **API** (`https://api.elevenlabs.io`), using an **API key** that a workspace admin creates. ConfigView sends only `GET` requests, plus read-only `POST` queries to the usage analytics endpoints. It never creates, changes or deletes anything in ElevenLabs.

You will end up with **1 required secret** (`ELEVENLABS_API_KEY`) in ConfigView when setup is complete.

> **Scope of this integration today.** ConfigView reads who has access to ElevenLabs and who is spending: the plan and quota, workspace members with seat type, groups and their members, service accounts and the **metadata** of their API keys (name, last characters shown as a hint, created and expiry dates, permission list, limits, allowed IP count), webhooks (destination host only), saved connections used by agents, the conversational AI agent inventory, MCP servers, daily usage per member, per key and per model, and the audit log on Enterprise. It does **not** read voices or voice samples, generated audio, conversation transcripts, agent prompts or knowledge bases, request logs, or API key values.

***

## What you need

* A workspace **admin** who can open **Settings > API Keys** in ElevenLabs. Groups, service accounts and webhooks need a key created by an admin.
* For audit logs: the **Enterprise** plan. On other plans that collector skips cleanly and the rest still runs.

***

## Step 1: Open the ElevenLabs page in ConfigView

Open ConfigView in a second browser tab and leave it open:

`https://{companyname}.configview.com/admin/integrations/elevenlabs`

***

## Step 2: Create the API key

1. In ElevenLabs open **Settings > API Keys** and choose **Create API Key**
2. Name it (for example `ConfigView`). Turn **Restrict Key** on and allow only these permissions, all read-only:

| Permission | Used for |
| - | - |
| `user_read` | Plan, quota and the key owner's seat |
| `workspace_read` | Groups, service accounts and their keys, webhooks, connections |
| `workspace_members_read` | Workspace members |
| `workspace_analytics_full_read` | Usage per member, key and model |
| `convai_read` | Agents and MCP servers |
| `audit_log_read` | Audit logs (Enterprise only) |

3. Copy the key now. ElevenLabs shows it once.
4. In the ConfigView tab paste it into `ELEVENLABS_API_KEY` under **Credentials** and save

The key does not rotate. You can set an expiry and an IP allow-list on it; if you use an allow-list it must include the address ConfigView runs from. Disable or delete the key in the same page to cut ConfigView off.

***

## Step 3: Connect and verify

1. Click **Connect**. ConfigView creates its tables and schedules every collector at your default run time:

| Script | Notes |
| - | - |
| **Subscription** | Plan tier, status, quota used, voice slots and overage. |
| **Workspace members** | Everyone in the workspace with seat type, owner and locked flags. |
| **Groups** and **Group members** | Groups with member counts, and who belongs to which. |
| **Service accounts** and **Service account keys** | Machine identities and the metadata of their keys. |
| **Webhooks** | Destination host only, events, status and last failure. |
| **Workspace connections** | Saved connections agents use, with type, provider and status only. |
| **Conversational AI agents** | Inventory with creator and last call time. |
| **MCP servers** | Destination host, approval policy and dependent agents. |
| **Usage by member**, **by API key**, **by model** | Daily usage for the last 30 days. |
| **Audit logs** | Last 30 days of workspace events (Enterprise). |

2. Click **Verify now**. The health check reads the secret, then reads the user and plan and the workspace member list.

If a check fails:

* **401 refused.** The key is wrong, deleted or expired.
* **401 missing permissions.** The key is restricted and lacks a permission from the table above.
* **403 or 404.** The key cannot read that area, or the plan does not include it.

***

## Data Tables

Each inventory table keeps only the newest run. Usage and audit tables keep a history of runs.

| Table | Source | Key Columns |
| - | - | - |
| `elevenlabs_subscription` | `GET /v1/user` | tier, status, character\_count, character\_limit, next\_reset\_at, voice\_slots\_used |
| `elevenlabs_members` | `GET /v1/workspace/members` | user\_id, email, first\_name, seat\_type, is\_owner, is\_locked |
| `elevenlabs_groups` | `GET /v1/workspace/groups` | group\_id, name, member\_count, usage\_limit, is\_scim\_synced |
| `elevenlabs_group_members` | `GET /v1/workspace/groups` | group\_id, member\_ref, ref\_is\_email |
| `elevenlabs_service_accounts` | `GET /v1/service-accounts` | service\_account\_user\_id, name, created\_at, key\_count |
| `elevenlabs_service_account_keys` | `GET /v1/service-accounts` | key\_id, name, hint, key\_ref, created\_at, expires\_at, is\_disabled, permissions, has\_admin\_permissions |
| `elevenlabs_webhooks` | `GET /v1/workspace/webhooks` | webhook\_id, name, url\_host, is\_disabled, is\_auto\_disabled, events |
| `elevenlabs_auth_connections` | `GET /v1/workspace/auth-connections` | connection\_id, name, auth\_type, provider, status |
| `elevenlabs_agents` | `GET /v1/convai/agents` | agent\_id, name, created\_at, last\_call\_at, is\_archived, creator\_email |
| `elevenlabs_mcp_servers` | `GET /v1/convai/mcp-servers` | server\_id, name, url\_host, approval\_policy, dependent\_agent\_count |
| `elevenlabs_usage_by_user` | `POST /v1/workspace/analytics/query/usage-by-product-over-time` | usage\_day, user\_id, product\_type, model, metric\_name, quantity |
| `elevenlabs_usage_by_key` | same, grouped by key | usage\_day, key\_ref, product\_type, quantity |
| `elevenlabs_usage_by_model` | same, grouped by product and model | usage\_day, product\_type, model, quantity |
| `elevenlabs_audit_logs` | `GET /v1/workspace/audit-logs` | event\_time, activity\_name, class\_name, actor\_email, ip\_address |

***

## Things worth knowing

**Usage is credits or cost.** Workspaces billed in credits use the credits analytics endpoint; workspaces billed by cost use the cost endpoint. ConfigView tries credits first and falls back to cost. Each usage row records `billing_mode`, `metric_name` and `unit` so the two are never added together.

**Keys are matched by a short reference.** ElevenLabs reports usage per key using a hash of the key. ConfigView keeps only its first 12 characters (`key_ref`), on both the key list and the usage rows, to tell you which key is spending. The key itself and the full hash are never stored. Usage made from the web app under a person's own session can appear without a key.

**No last-used time.** ElevenLabs does not report when a key was last used, so "unused key" is derived from the usage window. Seat type is the only role: there is no last sign-in or created date for members.

**Admin permissions.** A key is flagged `has_admin_permissions` when its permission list includes workspace write, service account write, user key creation, member invite or remove, group management, webhooks write or user write.

**Group members.** The API documents group members as plain strings. ConfigView records whether each looks like an email address (`ref_is_email`).

**Audit logs** need the Enterprise plan. Without it ElevenLabs answers 401 (missing permissions) or 403 and ConfigView writes nothing for that table without failing the run.

**Rate limit.** ElevenLabs limits **concurrent** requests per plan (HTTP 429) and publishes no per-minute number for these endpoints. ConfigView sends one request at a time, at most 60 a minute, and waits as long as ElevenLabs asks.

## What isn't collected

* Voices, voice samples and any generated audio or its links
* Conversation transcripts, agent prompts, knowledge bases and tool settings
* The API request log
* API key values and full key hashes
* MCP server headers, secret tokens and URL paths; webhook URL paths
* Saved connection credentials and tokens
* Invoices and billing details


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.