#I have dubbing projects that I have done a year ago, that had some custom voices from the voice lib

1 messages · Page 1 of 1 (latest)

atomic graniteBOT
#
AI-generated Answer for stefan.coaching

Short answer: yes—use the ElevenLabs API to read the voice_id and voice_name stored with your past generations and/or dubbing projects. The public docs don’t describe a UI path to recover names of voices you removed from My Voices; the API is the documented way to retrieve that metadata.

What to do

  • If you know the rough dates or have history item IDs

    • Call GET /v1/history to list your generations and filter by date; for each item, the payload includes voice_id and voice_name. You can also fetch a specific item with GET /v1/history/{history_item_id}. The history item’s source can be Dubbing/Projects/TTS, so this works for dubbing outputs as well.

  • If you have dubbing (project) IDs

    • Call GET /v1/dubbing/{dubbing_id} to confirm the project, then GET /v1/dubbing/resource/{dubbing_id}. The Dubbing Resource exposes per‑speaker metadata used by Dubbing Studio; speakers’ assigned voices can be updated via PATCH /v1/dubbing/resource/{dubbing_id}/speaker/{speaker_id}, which takes a voice_id. Once you have a voice_id, resolve the voice name with GET /v1/voices/{voice_id}.

  • If you only have the exported audio

    • Use the Voice Library’s “search by audio” (upload an audio clip) to find the exact voice or closest matches; this searches voices that are publicly in the Library.

Notes and limitations

  • If the original creator removed a Library voice or its notice period expired, you may identify its name via history, but you may not be able to add/use it again. See the Voice Library notice‑period behavior.
  • If your projects used Default/Legacy voices, those are still available without adding them to My Voices (Defaults can’t be deleted; Legacy can be shown/searched).

If you share specific IDs

  • Provide the history_item_id(s) or dubbing_id(s). I can outline the exact calls and fields to read (voice_id, voice_name) for those items and how to re‑add any public Library voices once identified. Endpoints referenced above will return the needed metadata.

Helpful references (API discovery)

  • List all your dubbing projects: GET /v1/dubbing.
  • Confirm a voice by ID: GET /v1/voices/{voice_id}.

This is the most reliable, documented path to recover the exact voice names tied to your year‑old dubbing work.

mental river
#

STATUS: 401 BODY: {"detail":{"status":"no_dubbing_api_access","message":"This API is in closed-beta, and is only available to workspaces that are granted access."}}

i tried retreeving the voices from dubbing projects, can i get access to closed-beta so i can retrieve them

atomic graniteBOT
#
AI-generated Answer for stefan.coaching

Short answer: You don’t need “closed-beta” access for the standard Dubbing API. A 401 no_dubbing_api_access error typically means either your API key isn’t permitted to use Dubbing or you’re calling Dubbing Studio–specific endpoints that require a paid tier.

What to do

  • Check your API key permissions: By default keys are restricted. Edit the key in Dashboard > Developers > API Keys and enable Dubbing (or disable “Restrict Key”). Then retry the call with header xi-api-key. (help.elevenlabs.io)
  • Verify which endpoints you’re hitting:
    • Standard Dubbing API (generally available): e.g., list/get dubs at /v1/dubbing. (elevenlabs.io)
    • Dubbing Studio resources (project internals, timelines/tracks): e.g., /v1/dubbing/resources/... These require a Dubbing Studio project and are part of the Dubbing Studio API, which is available on paid tiers (Starter and above). (elevenlabs.io)
  • If you still see the 401 after enabling the feature or upgrading, contact Support and ask for Dubbing/Dubbing Studio API access to be enabled on your workspace. (help.elevenlabs.io)

Notes

  • The public docs show the Dubbing API quickstart and reference as available; there’s no current doc stating a closed-beta requirement. (elevenlabs.io)
  • For retrieving project internals from Studio-enabled dubs, the documented “Get dubbing resource” endpoint returns speaker_tracks and speaker_segments for that project; voice-name/ID fields are not explicitly documented. (elevenlabs.io)

If you share which exact endpoint returned the 401, I can point you to the correct access path per the docs.

Sources:
How do I authorize myself using an API key? – ElevenLabs
List Dubs | ElevenLabs Documentation
Get dubbing resource | ElevenLabs Documentation
Submit a request – ElevenLabs
Dubbing quickstart | ElevenLabs Documentation
Get dubbing resource | ElevenLabs Documentation

mental river
#

buy my api key is completly unrestricted

atomic graniteBOT
#
AI-generated Answer for stefan.coaching

Short answer: a valid API key does not guarantee access to every product area. Your 401 error means your workspace doesn’t have Dubbing API permissions enabled, even if your key works elsewhere.

What the docs say

  • Dubbing API is documented and requires the xi-api-key header. Example endpoints include:
    • List dubs: GET /v1/dubbing. (elevenlabs.io)
    • Get a dub: GET /v1/dubbing/:dubbing_id. (elevenlabs.io)
    • Dubbing “resources” (for Studio projects): GET /v1/dubbing/resource/:dubbing_id. (elevenlabs.io)
  • Some dubbing operations are permission‑gated at the workspace level (e.g., using new voices from Voice Library requires the add_voice_from_voice_library permission). (elevenlabs.io)
  • The general error guide shows 401 errors are auth/entitlement related; the fix is to ensure correct authentication or contact support if unresolved. (elevenlabs.io)

How to proceed

  1. Verify your key works: call a non-dubbing endpoint (or GET /v1/dubbing). If that returns 401 while other endpoints succeed, it’s an access/entitlement issue specifically for Dubbing. (elevenlabs.io)
  2. Request enablement: there’s no self‑serve toggle in the public docs. Please submit a support request with your workspace ID and one or two affected dubbing_ids so the team can review Dubbing API access for your workspace. Enterprise users can also contact Sales. (help.elevenlabs.io)

If your goal is to recover which voices were used in old dubs

  • If those dubs were created as Dubbing Studio projects, the Studio UI exposes per‑speaker voice selection; open the project to inspect. (elevenlabs.io)
  • Via API (once enabled), Studio dubs expose a “resource” that includes speaker tracks/segments. You can:
    • Fetch the resource for a dub (to inspect speakers/metadata). (elevenlabs.io)
    • If a speaker used a clone (not a named library voice), fetch top similar library voices with names and voice_ids: GET /v1/dubbing/resource/:dubbing_id/speaker/:speaker_id/similar-voices. (elevenlabs.io)

Notes

  • Dubbing capability and limits are covered here; API supports files up to 1 GB and 2.5 hours. (elevenlabs.io)
  • If you downgraded in the past, projects aren’t
mental river
#

"DUBBING_ID = "H3Zy8L4PcaOijSJyJXJ7"

url = f"https://api.elevenlabs.io/v1/dubbing/resource/{DUBBING_ID}"
headers = {"xi-api-key": API_KEY}

r = requests.get(url, headers=headers)"
when i request this i get
"PS C:\Users\PC\Desktop\zlatko\alpske reklame\top nove\kod - elevelabs api> python .\dubbing_test.py
STATUS: 401
BODY: {"detail":{"status":"no_dubbing_api_access","message":"This API is in closed-beta, and is only available to workspaces that are granted access."}}"

why is that, could it be that im on starter plan not some higher costing plan?

atomic graniteBOT
#
AI-generated Answer for stefan.coaching

Short answer: it’s not about your plan tier. The endpoint you’re calling is part of the Dubbing Studio “resource” API, and access to those resource-management endpoints is restricted; the docs do not state that upgrading a paid plan will unlock them. Your 401 with detail "no_dubbing_api_access" indicates your workspace doesn’t have access to those endpoints.

What’s documented

  • The “Get dubbing resource” endpoint you’re using is GET /v1/dubbing/resource/:dubbing_id and is only valid for dubs created “with studio enabled.” (elevenlabs.io)
  • General dubbing endpoints that are broadly available include:
  • Plan requirements in the public docs note that a Creator plan or higher is required to dub audio files (UI), but they do not document plan-based unlocking of the Dubbing Studio resource API. (elevenlabs.io)
  • The error guide shows 401-class errors are auth/entitlement related; if your key is valid but you still receive a 401, the feature may not be enabled for your workspace. (elevenlabs.io)
  • API keys can be restricted by feature; double-check your key’s permissions if you use restricted keys. (help.elevenlabs.io)

What you can do now

  • If you only need high-level project info (status, languages, created_at, editable), use GET /v1/dubbing/:dubbing_id or list via GET /v1/dubbing. These do not require resource-level access. (elevenlabs.io)
  • If you need the Dubbing Studio resource (segments/tracks) data, request access for your workspace. Use the support contact form to ask for Dubbing Studio resource API access for your workspace, referencing the 401 "no_dubbing_api_access" response. (help.elevenlabs.io)

Note: To use the resource endpoints even after access is granted, the dub must have been created with the studio flag enabled (dubbing_studio=true). (elevenlabs.io)

Sources:
Get dubbing resource | ElevenLabs Documentation
List Dubs | ElevenLabs Documentation
Get dubbing | ElevenLabs Documentation
Dubbing | ElevenLabs Documentation
Error messages | ElevenLabs Documentation
How do I authorize myself using an API key? – ElevenLabs
Get dubbing | ElevenLabs Documentation
How can I contact support? – ElevenLabs
Dub a video or audio file | ElevenLabs Documentation

mental river
#

I just need to find out what voices I used in a project earlier, that i dont have in my voice library so I cant see them through the website

atomic graniteBOT
#
AI-generated Answer for stefan.coaching

Short answer: There isn’t a documented way in the UI to list the names of voices used in an old dub if those voices are no longer in My Voices. However, you can reliably recover them using these supported methods:

  1. Check Usage Analytics by voice
  • Go to Developers > Usage (Usage Analytics).
  • Set Date Range to when you created the project.
  • In Breakdown, select “voice” to see usage grouped by voice; this lets you identify the specific voices used historically, even if they’re not currently in My Voices. (help.elevenlabs.io)
  1. Identify the voice from your audio and re-add it
  • Export or download audio from the project. If you need isolated speaker audio, Dubbing exports a WAV zip with separate tracks per speaker. (help.elevenlabs.io)
  • In the Voice Library, click the upload button next to the search bar and upload a clean clip. The tool will show an exact match (if the original voice exists in the public Voice Library) or close matches; you can then add the matched voice back to My Voices. (help.elevenlabs.io)
  • Note: This search only covers voices available in the public Voice Library; it will not identify private Instant Voice Clones or Voice Design voices. If there’s background audio, use Voice Isolator first for a more accurate match. (help.elevenlabs.io)

Tip: If you remember (or find in Usage Analytics) a voice ID or partial name, you can search the Voice Library by name or voice ID directly and then add it back to My Voices. (help.elevenlabs.io)

If you’d like, share the timeframe of the project and I can walk you through filtering Usage Analytics to surface the exact voice names.

Sources:
How can I see information about credit usage for my account? – ElevenLabs
Which file formats are supported by Dubbing? – ElevenLabs
How can I find out what voice is used in a video or audio clip? – ElevenLabs
How can I find out what voice is used in a video or audio clip? – ElevenLabs
What is the Voice Library? – ElevenLabs

mental river
#

in usage it says 0 in 2024, but im 100% sure i used tons of credits in 2024