Webhook timeout: Timeout while sending request to

[JBradshaw6]

How do i extend my webhook timeout.  My API is going to take up to a minute to respond synchronously.  Will the HS Webhook process support this?

Jon

[GRajput]

Hi @JBradshaw6 

It is not possible to increase the Webhook timeout. One way to get this done is to send a status 200 after receiving data, and use a background job system or message queue to do the actual work(main coding part). fro this, you can use BullMQ / Redis Queue. For more details, you can look into official documentation of these on how to implement them in the code.

I hope this will help you out. Please mark it as Solution Accepted and upvote to help another Community member.
Thanks!

[suprdense · Accepted solution]

Hey @JBradshaw6 ,

You can’t extend HubSpot’s webhook timeout beyond 5 seconds. If your API takes longer, HubSpot marks the delivery as a timeout and retries up to 10 times over 24 hours.

The only reliable approach is to respond quickly within 5 seconds and process the payload asynchronously. Store the payload, acknowledge with a 2xx response, and handle the heavy logic in a background job or worker.

HubSpot doesn’t allow modifying the per-request timeout, only throttling and concurrency controls. Implement idempotency to avoid duplicate processing from retries and monitor webhook delivery metrics in your developer settings.

If this solution helped resolve your issue, please mark it as accepted and give it an upvote - it’ll make it easier for others with the same question to find the answer.

[d-lupo]

Hi @JBradshaw6,

It is not possible to extend the timeout duration for HubSpot webhooks. According to the official HubSpot API documentation, the current timeout for webhook requests is 5 seconds. If your webhook endpoint does not respond within this timeframe, HubSpot will return a timeout error and automatically retry the webhook delivery up to 10 times.

In your case I would respond immediately with a quick 2xx success status within the 5-second window to acknowledge the webhook. After this acknowledgment, any longer processing or tasks should be handled asynchronously in the background. 

[Jaycee_Lewis]

Thanks @d-lupo 🙌