Skip to content

fix: use /v1/voices for ElevenLabs key validation - #950

Merged
danielmiessler merged 1 commit into
danielmiessler:mainfrom
MarvinDontPanic:fix/elevenlabs-detect-endpoint
Mar 15, 2026
Merged

fix: use /v1/voices for ElevenLabs key validation#950
danielmiessler merged 1 commit into
danielmiessler:mainfrom
MarvinDontPanic:fix/elevenlabs-detect-endpoint

Conversation

@MarvinDontPanic

Copy link
Copy Markdown

Summary

  • Changed ElevenLabs API key validation from /v1/user to /v1/voices endpoint
  • The /v1/user endpoint requires user_read permission, which many API keys don't have
  • Keys with only TTS access fail validation even though they work perfectly for voice synthesis
  • Added handling for 401 missing_permissions response as "valid key, limited scope" — TTS works fine with a known voice_id regardless of permission scope

File Changed

Releases/v4.0.3/.claude/PAI-Install/engine/detect.ts

Test plan

  • Generate an ElevenLabs API key with default permissions (no user_read scope)
  • Run PAI installer — key validation should pass
  • Verify TTS voice playback works after installation

🤖 Generated with Claude Code

The /v1/user endpoint requires user_read permission, which many
ElevenLabs API keys don't have. Keys with only TTS access fail
validation even though they work perfectly for voice synthesis.

Changed to /v1/voices which works with basic API key permissions.
Also handles 401 missing_permissions as "valid key, limited scope"
since TTS works with a known voice_id regardless of scope.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@danielmiessler
danielmiessler merged commit fb07141 into danielmiessler:main Mar 15, 2026
tzioup pushed a commit to tzioup/LifeOS that referenced this pull request Aug 3, 2026
…labs-detect-endpoint

Better endpoint for key validation — the /v1/voices endpoint is more reliable across tier levels. Merged, thanks!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants