HTTP API Action Column Timeout Limits and Settings

Elias S. · 2025-11-28T11:53:29.980Z

Does the HTTP API action column have a max time before it times out? How high can you set it?

HTTP API Action Column Timeout Limits and Settings | Clay

14 comments

· Sorted by Oldest

Clay Support
APP
·
·
Yes, the HTTP API action column has a response timeout setting that you can configure in milliseconds. The sources don't specify the exact maximum timeout value you can set, but you can define it in the optional settings when configuring your HTTP API integration.
Clay Support
APP
·
·
Is that what you were looking for?
Elias S.
·
·
Yup – wondering if there a max time you can set it to? E.g. it will never go higher than 100 secs or so? (Appears to be the case when I test it) Would love to know if there is such a max time even with that max timeout value you can set in the HTTP API settings. Thanks!
Clay Support
APP
·
·
The documentation mentions that you can configure a response timeout in milliseconds for HTTP API columns, but it doesn't specify the exact maximum timeout value you can set. [1] There's also a reference to duration settings being between 1 and 900,000 ms for rate limiting, but this appears to be for rate limit duration rather than response timeout specifically.
What specific timeout value are you trying to set, and are you hitting an error when you go above a certain number?
Elias S.
·
·
Let's say that I wanted to set it to 300 seconds – is that possible?
Clay Support
APP
·
·
Based on the available documentation, there's a reference to duration settings being between 1 and 900,000 ms for rate limiting configurations. However, this appears to be specifically for rate limit duration rather than response timeout.
300 seconds would be 300,000 milliseconds, which falls within that 1-900,000 ms range mentioned in the sources. But the documentation doesn't explicitly confirm whether this same limit applies to response timeout settings.
You mentioned hitting what seems like a 100-second limit when testing - that suggests there might be a separate, undocumented maximum for response timeouts specifically.
Clay Support
APP
·
·
Did that answer your question?
Elias S.
·
·
No – please let me talk to a person
Clay Support
APP
·
·
I understand, I’ll connect you to one of our human agents who can assist you further.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
image.png(93 kB)
Kashif J.
·
·
Hi Elias, You should be able to see this "Response Timeout" optional parameter in your HTTP API column settings:
Elias S.
·
·
Yup tried setting that to 300000 but still times out after 100 sec
Bo (.
·
·
Hey Elias,
Got it, thanks for confirming that.
Right now there is an internal cap on the HTTP API column timeout, which is why your call is still timing out at around 100 seconds even when you set Response Timeout to 300000 ms. Anything above that cap won’t actually extend how long Clay will wait for the response.
If you need a longer-running process, the best pattern is usually to have your endpoint return sooner (within that ~100s window) and handle the long job asynchronously on your side, then write results back into Clay via a webhook or a follow-up call once they’re ready.
Let me know if you have more questions.
Elias S.
·
·
Exactly what I went for in the end - thanks a ton Bo!

Clay Support
APP
·
·
Yes, the HTTP API action column has a response timeout setting that you can configure in milliseconds. The sources don't specify the exact maximum timeout value you can set, but you can define it in the optional settings when configuring your HTTP API integration.
Clay Support
APP
·
·
Is that what you were looking for?
Elias S.
·
·
Yup – wondering if there a max time you can set it to? E.g. it will never go higher than 100 secs or so? (Appears to be the case when I test it) Would love to know if there is such a max time even with that max timeout value you can set in the HTTP API settings. Thanks!
Clay Support
APP
·
·
The documentation mentions that you can configure a response timeout in milliseconds for HTTP API columns, but it doesn't specify the exact maximum timeout value you can set. [1] There's also a reference to duration settings being between 1 and 900,000 ms for rate limiting, but this appears to be for rate limit duration rather than response timeout specifically.
What specific timeout value are you trying to set, and are you hitting an error when you go above a certain number?
Elias S.
·
·
Let's say that I wanted to set it to 300 seconds – is that possible?
Clay Support
APP
·
·
Based on the available documentation, there's a reference to duration settings being between 1 and 900,000 ms for rate limiting configurations. However, this appears to be specifically for rate limit duration rather than response timeout.
300 seconds would be 300,000 milliseconds, which falls within that 1-900,000 ms range mentioned in the sources. But the documentation doesn't explicitly confirm whether this same limit applies to response timeout settings.
You mentioned hitting what seems like a 100-second limit when testing - that suggests there might be a separate, undocumented maximum for response timeouts specifically.
Clay Support
APP
·
·
Did that answer your question?
Elias S.
·
·
No – please let me talk to a person
Clay Support
APP
·
·
I understand, I’ll connect you to one of our human agents who can assist you further.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
image.png(93 kB)
Kashif J.
·
·
Hi Elias, You should be able to see this "Response Timeout" optional parameter in your HTTP API column settings:
Elias S.
·
·
Yup tried setting that to 300000 but still times out after 100 sec
Bo (.
·
·
Hey Elias,
Got it, thanks for confirming that.
Right now there is an internal cap on the HTTP API column timeout, which is why your call is still timing out at around 100 seconds even when you set Response Timeout to 300000 ms. Anything above that cap won’t actually extend how long Clay will wait for the response.
If you need a longer-running process, the best pattern is usually to have your endpoint return sooner (within that ~100s window) and handle the long job asynchronously on your side, then write results back into Clay via a webhook or a follow-up call once they’re ready.
Let me know if you have more questions.
Elias S.
·
·
Exactly what I went for in the end - thanks a ton Bo!