Is the custom transcriber still works? I
# general-english
e
Is the custom transcriber still works? I set up for an assistant via api. I can see in the code but when i make a call i see on the logs using deepgramm stt not mine and on the dashboard i see error that i have to select a transcriber from the list. But there is no custom model.
f
Hey! I can definitely help with this. The issue is likely that custom transcribers set via the API aren't being recognized by the dashboard, which then overrides your config and falls back to Deepgram as the default STT. Quick question are you setting the custom transcriber at the assistant level in the API payload, or at the call/phone number level?
e
Assistan level
f
Got it. Can you share the relevant part of your API payload where you're defining the custom transcriber? That'll help me spot if there's a config issue causing it to be ignored and fall back to Deepgram.
e
I used this to patch my old assistant:
Copy code
curl -X PATCH https://api.vapi.ai/assistant/my-assistant-id \                                ─╯
    -H "Authorization: Bearer my-api-kex" \
    -H "Content-Type: application/json" \
    -d '{
      "transcriber": {
        "provider": "custom-transcriber",
        "server": {
          "url": "wss://mywebsite.com/api/custom-transcriber",
          "headers": {
            "x-vapi-secret": "my-api-key"
          }
        }
      }
    }'
and on the dashboar when I open the assistan and check the code I can see it has been set:
Copy code
"transcriber": {
    "server": {
      "url": "wss://mywebsite.com/api/custom-transcriber",
      "headers": {
        "x-vapi-secret": "my-api-key"
      }
    },
    "provider": "custom-transcriber"
  },
f
Can you send me a message if you don’t
Mind
y
i am facing the same issue. I called the PATCH api to https://api.vapi.ai/assistant/assistant-uuid with payload
Copy code
{
  "transcriber": {
    "provider": "custom-transcriber",
    "server": {
      "url": "wss://xxx.ngrok-free.app/api/custom-transcriber"
    }
  }
}
but it not use this endpoint. I check the log, it use deepgram
f
Thanks for sharing that your payload looks correct structurally. This looks like it could be a bug on Vapi's end where the custom transcriber config is being saved but not actually applied during calls. I'll escalate this and investigate. In the meantime, can you confirm if the PATCH request returns the updated transcriber config in the response?
e
sorry but who are you? I can open a support ticket too thank you
f
Am a freelancer who is more experienced in Ai voice agent