agentsclimarketplace

Elevenlabs common errors

Skill jeremylongshore/claude-code-plugins-plus-skills/skills/.curated/elevenlabs-common-errors

425 plugins, 2,810 skills, 200 agents for Claude Code. Open-source marketplace at tonsofskills.com with the ccpi CLI package manager.

Install
npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill elevenlabs-common-errors

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Diagnose and fix ElevenLabs API errors by HTTP status code. Use when encountering ElevenLabs errors, debugging failed TTS/STS requests, or troubleshooting voice cloning and streaming issues. Trigger with "elevenlabs error", "fix elevenlabs", "elevenlabs not working", "debug elevenlabs", "elevenlabs 401", "elevenlabs 429", "elevenlabs 400".

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

5.9 KB, as published. Nobody here has run it

ElevenLabs Common Errors

Overview

Quick diagnostic reference for ElevenLabs API errors organized by HTTP status code: run the connectivity probe, map the observed status code to a fix, then confirm with the debug checklist. This file is the fast index; the full per-error catalog (payloads + code fixes for every status code) lives in references/error-reference.md.

Prerequisites

  • ElevenLabs SDK installed
  • API key configured (ELEVENLABS_API_KEY)
  • Access to error logs or console output

Instructions

Step 1: Quick Diagnostic

Run the connectivity probe to isolate auth from quota from request problems:

# Test API connectivity and auth
curl -s -w "\nHTTP %{http_code}" \
  https://api.elevenlabs.io/v1/user \
  -H "xi-api-key: ${ELEVENLABS_API_KEY}"

# Check character quota
curl -s https://api.elevenlabs.io/v1/user \
  -H "xi-api-key: ${ELEVENLABS_API_KEY}" | \
  jq '.subscription | {tier, character_count, character_limit}'

# List available voices (confirms API access)
curl -s https://api.elevenlabs.io/v1/voices \
  -H "xi-api-key: ${ELEVENLABS_API_KEY}" | jq '.voices | length'

Step 2: Map the Status Code to a Fix

Match the HTTP status code (and the detail.status string in the response body) to its row below, then open the linked catalog entry for the exact payload and copy-paste fix:

Statusdetail.statusRoot causeFirst move
401invalid_api_keyKey missing/malformed/revokedRe-check ELEVENLABS_API_KEY, regenerate if needed
401quota_exceededMonthly character limit hitCheck usage, upgrade or enable usage-based billing
400voice_not_foundBad voice_id in pathGET /v1/voices to list valid IDs
400text_too_longTTS text > 5,000 charsChunk text with previous_text/next_text
400model_not_foundBad model_id stringUse an exact model ID (see catalog)
429too_many_concurrent_requestsOver plan concurrencyQueue requests to your plan limit
429system_busyElevenLabs under loadRetry with backoff (maxRetries)
422invalid_voice_sampleClone audio bad format/too shortMP3/WAV/M4A/FLAC, ≥30s, clean speech
WebSocket fails silentlyMissing xi_api_key / eleven_v3 on WSSend key in first WS message, use eleven_flash_v2_5

Full payloads, causes, and fix snippets for every row: references/error-reference.md.

Step 3: Debug Checklist

  1. Verify API key: curl -s https://api.elevenlabs.io/v1/user -H "xi-api-key: $ELEVENLABS_API_KEY"
  2. Check quota: Look at character_count vs character_limit in the response
  3. Verify voice_id: GET /v1/voices to list valid IDs
  4. Check model_id: Must be an exact match (see catalog)
  5. Check request size: Text must be under 5,000 characters
  6. Check concurrency: Are you exceeding your plan's concurrent limit?
  7. Check ElevenLabs status: https://status.elevenlabs.io

Output

Working through this skill produces:

  • A resolved HTTP status code and detail.status string identifying the exact failure.
  • The applied fix (corrected key/quota, valid voice_id/model_id, chunked text, request queue, or WebSocket handshake correction).
  • A clean re-run of the Step 1 probe returning HTTP 200 from /v1/user and a non-zero voice count, confirming the request path is healthy.

Error Handling

HTTPErrorRetryableAction
400Bad requestNoFix request parameters
401Auth/quotaNoCheck key or upgrade plan
404Not foundNoVerify voice_id/model_id
422ValidationNoFix input data format
429Rate limitYesBackoff + queue requests
500+Server errorYesRetry with backoff

Examples

401 after key rotation — the probe returns HTTP 401 with invalid_api_key. The old key is still in the shell env:

echo "${ELEVENLABS_API_KEY:0:8}..."   # confirms which key is loaded
# export the freshly generated key, then re-run the Step 1 probe → HTTP 200

429 under load — batch TTS returns too_many_concurrent_requests. Cap concurrency to the plan limit instead of firing all requests at once:

import PQueue from "p-queue";
const queue = new PQueue({ concurrency: 5 }); // Match your plan
await queue.add(() => client.textToSpeech.convert(voiceId, options));

400 on long input — a 7,000-character request returns text_too_long. Split it and preserve prosody across chunks:

const audio = await client.textToSpeech.convert(voiceId, {
  text: currentChunk,
  previous_text: previousChunk,  // Helps maintain flow
  next_text: nextChunk,          // Helps maintain flow
  model_id: "eleven_multilingual_v2",
});

See references/error-reference.md for the full payload and fix for every status code above.

Resources

Next Steps

For comprehensive debugging, see elevenlabs-debug-bundle. For rate limit handling, see elevenlabs-rate-limits.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.