Alex QS
11/21/2025, 2:52 AMbatman
11/21/2025, 2:36 AMmathes0n
11/21/2025, 2:04 AMJessica
11/21/2025, 12:49 AMSargey
11/21/2025, 12:07 AMJessica
11/20/2025, 9:09 PMMrCola
11/20/2025, 7:28 PMGoku_999
11/20/2025, 6:35 PMZeb
11/20/2025, 6:32 PMSamSEOClub
11/20/2025, 4:34 PMDhina
11/20/2025, 4:28 PMXainab Mehr
11/20/2025, 4:17 PMapplication/x-www-form-urlencoded format for POST requests, but I'm having trouble with VAPI tools.
WHAT I NEED TO SEND:
POST https://verify.twilio.com/v2/Services/{ServiceSid}/Verifications
Content-Type: application/x-www-form-urlencoded
Body: To=+13417668501&Channel=sms
WHAT I'VE TRIED:
1. API Request Tool:
- Set Content-Type header to application/x-www-form-urlencoded
- Configured body properties (To, Channel)
- Result: Twilio returns error 20001 "Missing required parameters"
- The body data isn't being sent
2. Found this Discord thread saying API Request tools are hardcoded to JSON:
https://discord.com/channels/.../API-Request-Tool-adds-default-Content-Type
Kyle mentioned "function tool will allow you to customize the header"
3. Function Tool:
- Added Content-Type: application/x-www-form-urlencoded header
- Configured parameters (To, Channel)
- Result: "No result returned" error
- Seems Function Tools expect to call my server, not external APIs?
QUESTIONS:
1. Is it possible to send form-encoded POST requests directly to external APIs with VAPI tools?
2. If yes, what's the correct configuration?
3. If no, do I need to create a backend proxy that reformats the request?
The API works perfectly in Postman with form-encoded data, just can't figure out how to make VAPI send that format.
Any guidance would be greatly appreciated!Pablito
11/20/2025, 3:20 PMronakp1234
11/20/2025, 12:40 PMMEDUSA 2.O
11/20/2025, 12:09 PMRelaximus
11/20/2025, 11:19 AMSTRANGE
11/20/2025, 8:45 AMnightcrawler
11/20/2025, 8:30 AMconorpo
11/20/2025, 7:08 AMrogerio
11/20/2025, 3:56 AMWater
11/20/2025, 1:02 AMhijaz
11/19/2025, 11:43 PMXainab Mehr
11/19/2025, 11:23 PMRobert_
11/19/2025, 8:43 PM/api/user/{{customer.number}}
When using this in a workflow or just a single assistant, we get this:
✅ /api/user/+1234567890 <---- working perfectly
When using the same assistant with the same tool in a squad, we get this:
⚠️ /api/user/{{customer.number}} <---- LiquidJS tag does not get replaced
The documentation around this is very confusing. Is there some difference in customer variables being passed around when using assistants in a squad?Xainab Mehr
11/19/2025, 7:48 PMKate
11/19/2025, 6:21 PMcrypticatul
11/19/2025, 2:46 PMRahul
11/19/2025, 12:32 PMsam_venturegrid
11/19/2025, 11:47 AM