Issue with userid Not Propagating to API Request i...
# supportv
VS893
06/10/2025, 7:05 AMDear Vapi Support Team,
I'm facing an issue where the userid variable passed from my frontend (Next.js) via assistantOverrides.variableValues isn't being received in the “API Request” step of my Vapi workflow. Although console logs confirm that userid is correctly set on the frontend, it consistently shows up as an empty string in my backend request.
Hardcoding userid directly in the workflow works fine, which suggests that dynamic interpolation of {{userid}} in the API Request step isn’t functioning as expected.
Could you help identify why {{userid}} isn’t being passed through correctly?
Thanks,
c
Chiranjeet Mishra
06/10/2025, 3:40 PMHey! To help track down this issue, could you share:
- The call ID
- When exactly this happened (the timestamp)
- What response you expected to get
- What response you actually got instead
This would really help us figure out what went wrong!
v
VS893
06/11/2025, 6:35 AMHi Shubham,
Thank you for your response. Here are the details you requested:
Call ID: 4c950f4b-fa22-4630-8192-eedec080893b
Timestamp: 10 June 2025, 13:06
Expected Response: successful extraction of userid which i am sending through frontend
Received Response: no userId is extracted, even though its correctly being sent from frontend to backend (did thorough debugging)
https://cdn.discordapp.com/attachments/1381892116694827108/1382246782888579172/2.png?ex=684a7521&is=684923a1&hm=ba8ebf3716cb72de3163ec9559c54fac035bb3bbd11adb348d609ffd9319027f&
https://cdn.discordapp.com/attachments/1381892116694827108/1382246783350083604/4.png?ex=684a7522&is=684923a2&hm=8c7e895fedaa38ee9f95cfb47ec3c2329b5cfcaaedb3c50ce881e6a7136ef83e&
https://cdn.discordapp.com/attachments/1381892116694827108/1382246783798743090/1.png?ex=684a7522&is=684923a2&hm=42d6dc961083507260943878d9fa441a0353ba56186873783ff49d3330659a61&
https://cdn.discordapp.com/attachments/1381892116694827108/1382246784348459060/3.png?ex=684a7522&is=684923a2&hm=f5dcc6a7a3c979313fda0738da455d23da71352904298ef526d3ef5d7069244a&
c
Chiranjeet Mishra
06/11/2025, 11:43 PMI am marking this ticket as solved, as we discussed over DMs.
o
Omar
07/02/2025, 4:13 PMHello, @VS893 @Shubham Bajaj could you please provide the solution because im facing the same problem ( its being passed as userId : "{{ userId }}" in the database )
c
Chiranjeet Mishra
07/02/2025, 9:02 PMHey! To help track down this issue, could you share:
- The call ID
- When exactly this happened (the timestamp)
This would really help us figure out what went wrong!
o
Omar
07/02/2025, 10:54 PMIn my web app, I’m using VAPI with an assistant that calls an API Request tool to generate interview questions. I pass userId from the frontend when starting the assistant.
The problem is that in the database, I see the literal string {{ userId }} instead of the actual user ID. It looks like the variable isn’t being replaced properly in the API Request tool payload.
I’m sure the userId is correct before the call, but it’s not sent right to the API.
this is my assistant ID : 9f902725-7f74-4a5b-adb4-3d71a7b975d7
and this is the api request tool id : e31aa610-285f-41e5-bd57-b742d88839b9
please check it and thank you.
Omar
07/02/2025, 10:55 PMthis from the code :
const handleCall = async () => {
console.log("Starting call with userId:", userId);
console.log("Starting call with userName:", userName);
setCallStatus(CallStatus.CONNECTING);
await vapi.start(ASSISTANT, {
variableValues: {
userId: userId,
username: userName,
},
});
};
and it's logging the id and username successfully
c
Chiranjeet Mishra
07/04/2025, 11:49 AMHey, we're looking into this and will get back to you soon.
2 Views