i cannot make gladia work and i cannot integrate gladia with the api please help https://cdn.discordapp.com/attachments/1454118259984040000/1454118260680163408/image.png?ex=698de329&is=698c91a9&hm=f0be1d920718e9bec9a2c5ae1a82d1e3e04d58629ae5a1f719c935f295f61868&

Suggestion: Double-check that your Gladia API key is active and correctly entered in the Vapi dashboard. If you continue to see "The provided credentials are not valid," try generating a new API key from your Gladia account and enter it again:

plaintext
1. Log in to your Gladia account.
2. Generate a new API key.
3. Copy and paste the new key into the Vapi Gladia integration field.

This often resolves credential errors caused by expired or invalid keys. For more details, see the [Gladia integration guide](https://docs.vapi.ai/providers/transcriber/gladia). Source: - [Gladia Transcriber Integration Documentation](https://docs.vapi.ai/providers/transcriber/gladia)

i used the native gladia and not working

Hi SamSEOClub, Please try these steps so we can pinpoint the issue quickly: 1. Verify API key & plan - Confirm the Gladia API key is active and not rate/usage limited (402 if free minutes exhausted). See the error pattern in related threads. - If unsure, generate a new key in your Gladia account and paste it into Vapi. 2. Test in Dashboard - Open your assistant > Transcriber tab > Provider = Gladia and click "Talk to Assistant" to test (removes telephony variables). See docs: https://docs.vapi.ai/providers/transcriber/gladia 3. Check Observe logs - Go to Observe > Call Logs and API Logs. Copy any call ID and the exact error (e.g., "gladia-transcriber-failed" or 402/invalid credentials). 4. Confirm transcriber config - Ensure language(s) and model are set correctly (e.g., set language to the target language or use automatic detection). For custom vocabulary or advanced settings, check changelog options if needed: https://docs.vapi.ai/changelog/2025/8/3 5. Try fallback - Configure a fallback transcriber/provider in the assistant in case Gladia fails. If you still have issues, reply with: - One failing Call ID from Observe > Call Logs - Exact error message from the logs - Whether you saw a 402 billing message or "credentials not valid" This info will let me investigate further.

this is not helping did u check the image?

As per your second image, you are using Gladia in a call. Were you able to identify the API key issue? If possible, please share your organization ID and a call ID where this issue is occurring. That will help us debug the problem from our side.

org id - 75e4953b-04ae-4adc-af2b-a5a2b0043717 callid - 019ba2d0-dcf8-7330-8550-94b4a3f03f67 can u help pls

Thanks for sharing. I can see the error in the logs. I’ll get back to you after some time once I have more information or a solution.