Skip to content
Log inSign up
Contact salesLog in

ElevenAPI Terms

Last updated: August 24, 2026

These ElevenAPI Terms (these “ElevenAPI Terms”) apply to your (“you”, “your” or “Customer”) access to and use of the Services through the API. They supplement your existing agreement with ElevenLabs or, if no separate agreement exists, the ElevenLabs Terms of Service applicable to you (either, the “Underlying ElevenLabs Agreement”). Your use of the API is also subject to our Prohibited Use Policy. Our processing of personal data in connection with the API is governed by the data protection terms of your Underlying ElevenLabs Agreement, including the DPA where one applies to you, and our Privacy Policy describes how we process personal data where we act as controller. Where you use the API to access a Service that is subject to its own Service-Specific Terms (“Service-Specific Terms”), those terms continue to apply to that Service, and these ElevenAPI Terms supplement them. Capitalized terms used but not defined in these ElevenAPI Terms have the meanings set forth in the Underlying ElevenLabs Agreement.

If you do not have a signed written agreement with ElevenLabs, you accept these ElevenAPI Terms by accessing or using the API, and you may not use the API if you do not agree to them or lack the authority to agree.

  1. The API.
    1. API. The “API” is the set of ElevenLabs application programming interfaces we make available, including our REST, streaming, and WebSocket endpoints and our official software development kits (“SDKs”), through which you access and operate the Services programmatically. The ElevenLabs command-line interface is governed by the ElevenLabs CLI Terms, and our Model Context Protocol features are governed by the ElevenLabs MCP Terms. These ElevenAPI Terms apply to every API call made through either. This description does not create any representation, warranty, or other commitment as to the API.
    2. Availability of Endpoints. The endpoints, models, capabilities, and parameters available to you depend on your plan, entitlements, and region, and we do not warrant that any of them is or will remain available to you. In particular, where we make a Service available in an isolated regional environment, that environment is a separate workspace with its own endpoints and credentials and may not include every Service, endpoint, model, or capability available elsewhere. Your decision to purchase or use the Services was not and is not contingent on the availability of the API or of any endpoint, model, or capability.
    3. Fees, Limits, and Versions. Usage of the Services initiated through the API is billed in accordance with your plan or Order Form, as applicable, and counts toward the rate, concurrency, and entitlement limits applicable to you. We may introduce or change those fees and limits on notice in accordance with the Underlying ElevenLabs Agreement, and may release, change, deprecate, or discontinue versions of the API subject to any notice or transition period that agreement requires.
    4. Open Source. Where an SDK is made available under an open-source license, that license governs your rights in the SDK software, and nothing in these ElevenAPI Terms limits or supersedes it. That license does not, however, grant any right to access or use the Services, which the Underlying ElevenLabs Agreement and these ElevenAPI Terms govern.
    5. Documentation. “Documentation” means our then-current technical and functional documentation for the Services and the API, including the documentation published at https://elevenlabs.io/docs and any documentation we otherwise make available to you. You will access and use the Services through the API in accordance with the Documentation, including the limits, intervals, formats, and integration requirements it specifies. We may update the Documentation from time to time.
  3. Credentials and Attribution.
    1. Authentication. Access to the API is authenticated using the methods we make available, which may include user and service account API keys, OAuth credentials, and the short-lived tokens and signed access URLs we issue for authenticating access to the API (each, a “credential”).
    2. Your Credentials. You are responsible for each credential used with the API, including for issuing, storing, rotating, and revoking it, and for applying the scope, quota, expiry, and network or address restrictions that are available for that credential and appropriate to its intended use. You will not share a credential outside your organization, and will issue separate credentials for separate applications, environments, and users.
    3. No Client-Side Exposure. You will not embed, transmit, or otherwise make any API key, OAuth client secret or refresh token, webhook signing secret, or other secret we issue to you available in any browser, mobile application, or other client or artifact accessible to a third party, and you will call the API using an API key only from a server or other environment you control. Where you enable access to the Services from a client, you will use the short-lived tokens, signed access URLs, OAuth flows designated for client-side use, or other client-side access methods the Documentation describes for the relevant Service, and configure the access controls the Documentation makes available. You will promptly disable, revoke, and replace any API key or other secret you have reason to believe has been exposed.
    4. Attribution. Each API call, and all resulting access to and use of the Services, is attributed to the account and workspace associated with the credential used. That activity is treated as your action and is your responsibility, whether initiated by a person or by a script, a continuous integration or deployment pipeline, a coding assistant, or any other AI tool or automated process (each, an “Automated Process”), and whether or not you authorized it, except to the extent it results from our breach of our security obligations under the Underlying ElevenLabs Agreement. You will notify us promptly on becoming aware of any unauthorized access to or use of the Services through a credential associated with your account or workspace.
  5. Your Customer Applications. A “Customer Application” is any application, product, or service of yours through which you access the Services through the API, and has the meaning given in the Underlying ElevenLabs Agreement where that agreement defines it. You are responsible for each Customer Application, including for authenticating and authorizing its users and for ensuring that a user cannot access Services resources, including agents, voices, conversations, and generated files, that you have not authorized that user to access. Your credentials are not a substitute for access controls in your own systems.
  6. Integration Requirements.
    1. Rate Limits, Concurrency, and Retries. You will design and operate each integration to observe the rate, concurrency, and usage limits applicable to you, to handle throttling and error responses using exponential backoff rather than repeated immediate retries, to wait for requests in flight to complete rather than retrying where you have reached a concurrency limit, and to poll no more frequently than any interval we publish.
    2. Asynchronous Results and Webhooks. Where a Service returns results asynchronously or delivers them by webhook, you are responsible for operating and securing your receiving endpoint. You will verify the signature on each delivery before acting on it, and you bear the risk of acting on any delivery you have not verified. Because we may deliver the same event more than once, you will handle deliveries idempotently. We may disable delivery to an endpoint that repeatedly fails or is unreachable, and requests that target a disabled endpoint may be rejected. Where we make results available by expiring signed URL, you are responsible for retrieving and storing them before expiry, and, except as the Documentation expressly provides, we have no obligation to retain them or to reissue access to them.
    3. Version Compatibility. You will design each integration to tolerate additive changes, including by ignoring response fields, values, and headers it does not recognize and by not applying strict type checking to responses, and not to depend on undocumented behavior.
  8. Scope of Our Security and Data Commitments. Our security and data protection commitments under the Underlying ElevenLabs Agreement, including under the Security Addendum and the DPA where each applies to you, apply to Customer Content or Content, as applicable, within the systems we control. They do not apply to any system or environment you or a third party controls, including your servers, applications, repositories, and any Automated Process, or to any credential, configuration, or Customer Content or Content held in any of them.
  9. Your Content. Data, information, and material you provide to the Services through the API, and any Output generated in connection with the API, constitute Content or Customer Content, as applicable, and may be used by us as provided in the Underlying ElevenLabs Agreement. You will not use the API to transmit to us any data you are prohibited from submitting under the Underlying ElevenLabs Agreement or the applicable Service-Specific Terms, including Prohibited Data as defined in those terms. You will not transmit protected health information to us through the API except as permitted by an executed business associate agreement, as permitted by applicable law, or as we have otherwise expressly agreed in writing. You will not permit any person or Automated Process acting on your behalf or using your credentials to do anything these ElevenAPI Terms prohibit you from doing.
  10. General.
    1. Service-Specific and Model-Specific Terms. Your access to and use of particular Services or models through the API may be subject to additional terms that apply to them (the “Service-Specific Terms” and the “Model-Specific Terms” respectively and, together, the “Applicable Service Terms”), which supplement and form part of these ElevenAPI Terms as they relate to your use of the API.
    2. Beta Services. Where we designate the API, or any endpoint, model, or capability, as alpha, beta, pilot, preview, or a similar designation, the Beta Services provisions of the Underlying ElevenLabs Agreement apply to it, or, if you are subject to the ElevenLabs Terms of Service, the Beta Services Addendum applies to it. Those provisions prevail over these ElevenAPI Terms in the event of a conflict, solely as to the endpoint, model, or capability so designated.
    3. Suspension. We may suspend or restrict your access to the Services through the API, or disable a credential used with the API, where we reasonably determine this is necessary to address a violation of these ElevenAPI Terms, the Prohibited Use Policy, or the Underlying ElevenLabs Agreement, a compromised or misused credential, or a risk to the security, integrity, or availability of the Services. Where practicable we will notify you first and give you a reasonable opportunity to resolve the issue, and we will restore access promptly once it is resolved. This Section is in addition to any suspension or termination right under the Underlying ElevenLabs Agreement. Where we suspend or restrict your access to the Services generally, we will do so in accordance with the Underlying ElevenLabs Agreement and the notice and cure periods in that agreement do not apply to disabling or restricting an individual credential.
    4. Support. Our support commitments under the Underlying ElevenLabs Agreement, where you have them, apply to the Services. They do not extend to any Customer Application, integration, or SDK as implemented, configured, or run in your environment, or to any third-party software or dependency required to run it. 
    5. Order of Precedence. If there is a conflict, the following order applies to your access to and use of the Services through the API: (a) any term of the Underlying ElevenLabs Agreement or an Order Form that expressly addresses the API; (b) the ElevenLabs CLI Terms and the ElevenLabs MCP Terms, solely as they relate to the CLI or an MCP Feature; (c) the ElevenLabs Music API Terms, solely as they relate to your access to and use of the Music Service (as defined in the ElevenLabs Music Terms); (d) the Applicable Service Terms; (e) these ElevenAPI Terms; and (f) the remainder of the Underlying ElevenLabs Agreement. These ElevenAPI Terms do not modify the confidentiality, indemnification, or limitation of liability provisions of the Underlying ElevenLabs Agreement.
    6. Updates. We may update these ElevenAPI Terms. Updates take effect when we post them, except that, if you have a signed written agreement with ElevenLabs, an update that materially reduces your rights takes effect 30 days after we notify you. Updates required by law, or that we reasonably determine are necessary to address a legal, safety, or security risk, take effect immediately.

Create with the highest quality AI Audio

Sign up