ElevenLabs · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for ElevenLabs API Documentation API Key API

3 actions 3 updates phrasing extends openapi/elevenlabs-api-key-api-openapi.yml

Generated by API Evangelist Written by API Evangelist tooling for ElevenLabs's API. It is a proposal applied on top of the contract, not a document ElevenLabs publishes.

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 3

$.info

$.paths['/v1/workspaces/api-keys/disable'].post

$.paths['/v1/workspaces/api-keys/third-party-disabling'].post

OpenAPI Overlay

# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for ElevenLabs API Documentation API Key API
  version: 1.0.0
extends: openapi/elevenlabs-api-key-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 2
- target: $.paths['/v1/workspaces/api-keys/disable'].post
  update:
    x-apievangelist-phrasing:
      intent: Disable the API key making this request
      effect: destructive
      questions:
      - How do I shut off an API key that I think has leaked, using the key itself?
      - What confirmation is required before an API key can disable itself?
      instructions:
      - text: Disable the API key I'm calling with, confirming with api_key_name {api_key_name}.
        slots:
          api_key_name: query.api_key_name
      - text: Kill this exposed ElevenLabs key now by self-disabling it.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/v1/workspaces/api-keys/third-party-disabling'].post
  update:
    x-apievangelist-phrasing:
      intent: Set whether found keys can be disabled by anyone
      effect: write
      questions:
      - Can I stop third parties who find one of our keys from disabling it?
      - Is there a workspace-wide policy for whether a key holder may disable a key?
      instructions:
      - text: Set the workspace third-party key disabling policy to {third_party_disable_allowed}.
        slots:
          third_party_disable_allowed: requestBody.third_party_disable_allowed
      - text: Allow anyone holding one of our workspace keys to disable it.
      method: generated
      generated: '2026-09-26'

Work with this as data

Every overlay here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for openapi overlays

4 MCP tools reach this

find_overlaysBrowse and filter every overlay in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This overlay

curl "https://apis.io/api/v1/overlays/elevenlabs-api-key-api-phrasing-overlay"

All openapi overlays

curl "https://apis.io/api/v1/overlays?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.