Skip to main content
ElevenLabs workspace usage sits on a separate bill from AWS, GCP, and Azure. Connect with a workspace API key so that spend lands in with your other billing datasources. This connector imports workspace usage from the usage query API. Costory stores it as a billing datasource, the same as other SaaS billing sources.
1

Create a workspace API key

In ElevenLabs > Developers / API keys, create a workspace API key (typically sk_...). Copy it immediately. It is shown once.
2

Grant Workspace analytics, full read

Grant Workspace analytics, full read (workspace_analytics_full_read). Restrict the key to analytics if the UI allows. A key without this scope cannot ingest usage.
3

Connect in Costory

Go to Integrations, click + Add integration, then choose ElevenLabs under Billing. The connect URL is /integration/new/elevenlabs/billing.
4

Enter connection details

Fill Connection name (default ElevenLabs) and API token.Region is optional and only needed for isolated residency hosts. Leave it on Global (api.elevenlabs.io) unless this workspace lives on a residency host. The wrong region looks like a bad key. See ElevenLabs data residency.Start date is optional. Leave it empty to use Costory’s default lookback.
5

Validate, then save

Click Validate. Costory calls the workspace usage query with xi-api-key. Save stays disabled until the key can read workspace usage. An empty usage window is still success. If this is the only billing source and it is demo data, Costory asks you to confirm before replacing it.
On first sync, Costory backfills up to 12 months of workspace usage, depending on what ElevenLabs retains. New data then follows the usual data refresh cadence. SaaS sources typically appear in about 10 minutes.

​
Field reference

​
What Costory includes

Costory pulls workspace usage from ElevenLabs’ Get workspace usage API and maps it into . Typical lines are billed workspace usage by product over time for that account. How to analyze ElevenLabs costs
  • Spend by product: group by Service name or SKU
  • Spend over time: use the same date presets as other billing sources in Explorer
What Costory does not include
  • Per-voice (voice_id) or per-member email splits
  • Taxes, credits, or invoice adjustments outside the usage query
  • Inference keys that are not workspace API keys
Rotate the API token from Integrations when you need a new credential. The stored region stays the same. A residency move is a different workspace and key: create a new datasource.

​
Troubleshooting

Billing Data

All billing providers and shared setup notes.

Kling AI billing

Connect Kling Open Platform unit deductions.

OpenAI billing

Import OpenAI Platform organization costs.

Explorer

Filter and group ElevenLabs spend with the rest of your stack.
Last modified on September 16, 2026