Skip to content

fix(auth): explain missing API key permissions - #126

Closed
tgolob wants to merge 1 commit into
elevenlabs:mainfrom
tgolob:fix/api-key-scope-feedback
Closed

fix(auth): explain missing API key permissions#126
tgolob wants to merge 1 commit into
elevenlabs:mainfrom
tgolob:fix/api-key-scope-feedback

Conversation

@tgolob

@tgolob tgolob commented Aug 22, 2026

Copy link
Copy Markdown

Fixes #80

Summary

  • inspect the ElevenLabs error body before classifying HTTP 401 responses as invalid keys
  • explain that missing_permissions requires the Conversational AI read (convai_read) permission and link directly to API-key settings
  • keep invalid/expired keys, other access denials (including IP restrictions), network failures, and unexpected errors distinct

Test plan

  • jest --testPathIgnorePatterns='e2e' --runInBand — 20 suites, 249 tests passed
  • tsc --noEmit
  • eslint src -c eslint.config.js — 0 errors (11 pre-existing warnings in unrelated tests)

@PaulAsjes

Copy link
Copy Markdown
Collaborator

Thanks for the contribution, but we just released v1 which is a complete rewrite in Rust, making this obsolete.

@PaulAsjes PaulAsjes closed this Aug 24, 2026
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.

Provide detailed feedback when using a poorly scoped key

2 participants