https://vapi.ai/ logo
Join Discord
Powered by
Custom Tool get method.
# support
b
Is there a way to have my custom tool do a get request instead of post.
c
I've been struggling with this as well. Had to switch everything to POST for now
c
Here is an example:
Copy code
curl -X POST https://api.vapi.ai/tool \
  -H "Authorization: Bearer YOUR_VAPI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "function",
    "function": {
      "name": "getNumberFact",
      "description": "Get an interesting fact about a number",
      "parameters": {
        "type": "object",
        "properties": {
          "number": {
            "type": "integer",
            "description": "The number to get a fact about"
          }
        },
        "required": ["number"]
      }
    },
    "server": {
      "url": "http://numbersapi.com/{number}",
      "method": "GET",
      "headers": {
        "Accept": "application/json"
      }
    }
  }'
y
it does work with a curl request but same issue when using the tools
Copy code
{
  "status": "error",
  "timestamp": "2025-11-21T00:23:34.457Z",
  "path": "/v2/slots/available?eventTypeId={{eventTypeId}}&startTime={{startTime}}&endTime={{endTime}}&timeZone={{timeZone}}",
  "error": {
    "code": "NotFoundException",
    "message": "Cannot POST /v2/slots/available?eventTypeId={{eventTypeId}}&startTime={{startTime}}&endTime={{endTime}}&timeZone={{timeZone}}",
    "details": {
      "message": "Cannot POST /v2/slots/available?eventTypeId={{eventTypeId}}&startTime={{startTime}}&endTime={{endTime}}&timeZone={{timeZone}}",
      "error": "Not Found",
      "statusCode": 404
    }
  }
}
c
Hi there, Thanks for sharing the PCAP — I reviewed the capture, and the root cause of the 403 Forbidden is clear. Summary of Findings The failure is happening on Twilio’s side due to SIP authentication errors. Twilio returns: 
X-Twilio-Error: 32202 Authentication failure - bad user credentials
The SIP flow shows Twilio receiving your INVITE and immediately responding with a 403 Forbidden, meaning the request reached Twilio successfully, but the credentials did not match. Here’s what we recommend: 1. Verify your Twilio SIP Credentials - SIP username - SIP password Make sure they’re the current values and weren’t recently rotated. 2. Confirm the SIP Domain The domain in the request resolves to: 
nexteam@zendesk.sip.twilio.com
Ensure this exact SIP domain is configured correctly in your Twilio console. 3. Regenerate Credentials if Needed If there's any doubt, regenerate your SIP credentials in Twilio and update them in your Vapi SIP trunk settings. 4. Check Twilio SIP Logs Twilio will show more detailed authentication failures under your SIP Domain logs. The good news: This is not a network or firewall issue. Your packets reach Twilio correctly — the issue is strictly an authentication mismatch.
b
Sorry this might be a dumb question but where would I actually paste this. VAPI doesn’t allow you to edit the json does it?
c
Unfortunately no. You would have to use the API endpoint to make this change.
3 Views
PreviousNext
Powered by