Urgent - Unable to pass variable to API Request To...
# support
g
Hi, I’m trying to pass dynamic parameters (for example organization_id and agency_id, these are catched in assistant-request hook) in the HTTP request made by the API Request tool. The Liquid syntax is displayed, but the values are never resolved. The same variables, however, are correctly populated both in the prompt and in the welcome sentence. Without this functionality, the API Request feature loses much of its usefulness, and it seems strange to me that the documentation does not include any example showing how to pass dynamic parameters—after all, passing parameters to an API is a fundamental use case. I’d like to understand whether there’s a specific step needed to enable variable resolution in API Request, or if this is a known bug/limitation. Thanks in advance. https://cdn.discordapp.com/attachments/1409872383912710224/1409872384567148716/Screenshot_2025-08-26_alle_14.08.59.png?ex=68aef57a&is=68ada3fa&hm=b736d6b2861c03471b2331bcb2ee20887deaee0989f7937c34b935a2d92ef05d&
c
Hi Giovanni, We replied to your other ticket but in case you didn't receive it, could you please provide a call id where this API request tool is being used?
g
Hello Kyle, we can discuss here in order to share information with community. Call ID: 3f7a1320-4592-49ab-ba17-ab7f153edf42
When I call the phone number, no assistant is associated to it, in this way the webhook is called with event type assistant-request, in this point I return the variable that I want save in the context of call: https://cdn.discordapp.com/attachments/1409872383912710224/1410621274077794395/Screenshot_2025-08-28_alle_15.33.55.png?ex=68b1aeef&is=68b05d6f&hm=567e073261b8b06b1179d15d0ee793853e5090450dd667c111684b0392538614&
The assistant is properly associated and variables are properly rendered in welcome sentence (the assistant replace liquid syntax with the value I passed in webhook) https://cdn.discordapp.com/attachments/1409872383912710224/1410621808155295865/Screenshot_2025-08-28_alle_15.46.14.png?ex=68b1af6f&is=68b05def&hm=0188a28c1ee2278ff018fc14eeafc3241a406ece0dd575bb33f63e4f6d7fdeef&
At this point I think "Ok, if the assistant speak the right values, it means that also {{organization_id}} and {{agency_id}} are available, I can use it to send request to API Request: https://cdn.discordapp.com/attachments/1409872383912710224/1410622239597924352/Screenshot_2025-08-26_alle_13.59.51.png?ex=68b1afd6&is=68b05e56&hm=2e9fa9fcd60746b3eceb9a94e5acc674488d2134504ec62e0b734406050951ba&
I don't want replicate tool just because I'm unable to pass parameters in API Request Tool, it seem very very strange I'm unable to perform this action.
Furthermore I have also another problem, because I can receive the invocation but I can't see any information about call_id, I would discriminate the call_id which triggered the invocation
c
We will check with the team on this and get back to you. If your assistant is able to iterate the correct values from the liquidJS format, then it should be able to use those in the url to our knowledge.
g
Any update about it?
c
Yes, dynamic variables should be working in the URL. Could you please try using some different variables to see if they populate?
g
I've also tried with {{customer.number}} which is a vapi reserved variable but it still doesn't rewrite (the value passed is "{{customer.number}} ") This feature should be working as you said but it doesn't. Please provide a support for this ticket. https://cdn.discordapp.com/attachments/1409872383912710224/1415516004707995749/Screenshot_2025-09-11_alle_03.50.06.png?ex=68c37d82&is=68c22c02&hm=50edbca3a3d3176a9eb9028f74b560e27039b51c1b745f7eb60760dc5a5a887b&
Show me how you are able to do it, with screenshot, try to rewrite the customer.number variable
c
We apologize for the delay in responses lately. We are in process of making some changes to our workflow in how we handle support requests. The good news is that we are starting to get back on track of having a 48 hour response time and we would like to start cleaning up anything old. With that being said, just wanted to check in with you to see if you have made any progress or changes to your project since support has last reached out.
g
Hello Kyle I'm still waiting a solution for it. I'm creating tools for each assistant as workaround but as you can understand this is not scalable as approach. If you are agree we could schedule some meet on your calendly and we can check together what is the break point. Thank you, and let me know (also DM).
3 Views