VAPI•5d ago

Workflow API request timeout

We have a workflow for appointment bookings that is close to getting to production.

The issue I am facing is that the API request nodes seem to timeout after 5 seconds, even if I set the timeoutSeconds to a bigger value. Please fix this as soon as possible, or let me know what I need to change, since we are on a tight timeline.

Vapi Support BotAPP•12/12/25, 2:00 PM

The API Request node supports a timeoutSecondstimeoutSeconds parameter, which should let you set a custom timeout for your API calls.
If your configuration looks like this but still times out after 5 seconds, the issue may be outside the documented settings:

{
  "type": "apiRequest",
  "url": "https://your.api/endpoint",
  "method": "POST",
  "timeoutSeconds": 20
}

{
  "type": "apiRequest",
  "url": "https://your.api/endpoint",
  "method": "POST",
  "timeoutSeconds": 20
}

If the timeout is not being respected, please contact Vapi support directly, as the documentation does not mention a workaround for this issue.
For reference, see the API Request node documentation.

Source:

API Request Node Documentation

⤵️ Mention @Vapi Support Bot for follow-ups 🐥

popular-magentaOP•12/12/25, 2:01 PM

Yes timeout is not being respected

unexpected-ivory•12/12/25, 6:31 PM

It looks like your API nodes are hitting a default 5-second connection timeout, which isn’t always controlled by timeoutSeconds. I usually check both the SDK/client settings and any gateway limits, and for longer requests, consider using async handling or background jobs. This approach avoids blocking the workflow while keeping it stable. Are these API calls going to internal VAPI endpoints or external services?
@Pedro Lourenco

popular-magentaOP•12/12/25, 8:30 PM

They are going to external services.

unexpected-ivory•12/12/25, 9:58 PM

Since your calls hit external services, the best fix is to move them through an async handler or a small proxy layer so the workflow doesn’t get stuck on the 5-second limit. This keeps everything stable and production-ready. If you want, we can continue privately and I’ll walk you through the exact setup.
@Pedro Lourenco

popular-magentaOP•12/13/25, 8:50 AM

Sure that would be good. So you can confirm that there is no way around the 5 second limit, right?
The issue is that in some steps I need the response from the workflow before I can proceed to the next step, e.g. get the times available. Will the async handler cause issues when it comes to this?
The backend is custom coded by us, so I think we can just change the code, according to your recommendation, instead of using a proxy right?

unexpected-ivory•12/13/25, 9:11 PM

You’re right, since some steps need immediate responses, we need to handle this carefully. Given that your backend is custom, there are options like adjusting the code to manage longer requests directly instead of adding a proxy. Let’s discuss privately so I can walk you through the best approach and make sure nothing in the workflow breaks.
@Pedro Lourenco

popular-magentaOP•12/15/25, 6:34 AM

Are you a Vapi employee?

unexpected-ivory•12/15/25, 11:36 AM

No, I’m not a Vapi employee. I’m an independent specialist who works hands-on with Vapi workflows and production API integrations.
@Pedro Lourenco