Ovi1kanobe
10/13/2025, 7:55 PMVapi Support Bot
10/13/2025, 7:56 PM{{start}}, {{end}}, and {{timezone}} are substituted correctly, define them as top-level parameters in your tool configuration, not just in the request body. For example:
json
{
"parameters": {
"start": { "type": "string", "description": "Start time" },
"end": { "type": "string", "description": "End time" },
"timezone": { "type": "string", "description": "Time zone" }
},
"url": "https://api.cal.com/v2/slots?eventTypeSlug=consultation&username=sailboatai&start={{start}}&end={{end}}&timeZone={{timezone}}"
}
Update your tool config to include these parameters at the top level, then test again.
For more, see the [custom tools guide](https://docs.vapi.ai/tools/custom-tools).
Source:
- [Custom Tools](https://docs.vapi.ai/tools/custom-tools)Ovi1kanobe
10/13/2025, 8:05 PMOvi1kanobe
10/13/2025, 8:07 PMVercel
10/13/2025, 9:39 PMChiranjeet Mishra
10/14/2025, 7:21 PMtype, method, url, and other relevant data according to the [API Reference](https://docs.vapi.ai/api-reference/tools/update).
If the type is apiRequest, the object should include method, url, and credentialId along with any necessary headers and body. Check if the rejectionPlan and variableExtractionPlan are properly defined to manage any issues arising during the request execution.
Also, keep in mind the CreateApiRequestToolDto configuration, and ensure that all required fields are correctly set up, which may impact how the parameters are recognized and executed during tests or actual requests.
For detailed steps, you can reference the [SDK documentation](https://docs.vapi.ai/api-reference/tools/update) to ensure your implementation follows the required specifications.