API call custom llm
# support
y
Can someone tell me how the Authorization header for the API call to the custom llm works? Is this Bearer? Every time I ask something the assistant just does not respond ... and the API endpoint of the custom llm works (tested with Postman)
v
@Yestix Yes, typically when you're working with APIs that require authentication, the
Authorization
header is used to include the necessary credentials. If the API uses a Bearer token, you would include it in the header like this:
Copy code
Authorization: Bearer YOUR_API_TOKEN
Make sure to replace
YOUR_API_TOKEN
with your actual API key. If you're having trouble with the assistant not responding, it could be due to various reasons such as network issues, incorrect API key, or improper request formatting. If you've confirmed that the API endpoint works with Postman, ensure that you're using the same headers and request body in your code. If you need further assistance with the API call or have any other questions, please let me know!
You can continue this conversation by mentioning me in the message.
y
@User The bot's answer is in general but does not explain the situation for VAPI
s
can you please share the cal id to help you better.
use the api bearer authentication.
y
I did, however it seems I can't get it to work. This is a call ID as an example: bd06638b-fcf9-46dd-9396-1d802560998f
m
+1 is there something wrong with custom llm? i've setup the integration of Vapi with voiceflow recently and it worked fine but now it doesn't work, i've set my assitant to a custom llm and an ngrok url but it seems to never do a post request to that ngrok server assistant id: 60487333-df9b-46fc-9570-87efc564fcb8
as more reference currently im getting on vapi-events and it never queries the custom llm url i've put (even if its not found it must show 404 here) https://cdn.discordapp.com/attachments/1270385142887743488/1270762067422351503/image.png?ex=66b4e0e6&is=66b38f66&hm=ad110e9a586f2170ff6ccd829116f1f09f491ab86a6cb3873f2a9e241db5c725&
s
please create a new support ticket for this.
@Yestix we are sending the request to the LLM but we didn't heared the response back. please share the repo or code snippets.
y
@Shubham Bajaj I fixed it by reinstalling the custom LLM. There was no issue on the VAPI end. Thanks for helping out!