Hi everyone, We’re creating a custom API endpoint to fetch some data inside Clay. We’ll be sending a GET request. How much time will Clay wait for the response? We want to make sure we don’t run into a ERROR TIMEOUT, as a single request can take up to 30 minutes.
Based on the available information, Clay doesn't specify an exact timeout limit for API requests. However, you can configure rate limits in the HTTP API settings to control request frequency. For requests that may take up to 30 minutes, you might need to implement a wrapper solution using tools like Replit or Make that can handle longer processing times. Could you share more details about your API endpoint and what kind of data you're trying to process that takes 30 minutes?
i think current limit is 1 minute, 30min is going to timeout for sure
bot is right about make/n8 etc
Clay doesn't specify an exact timeout limit for API requests, but based on your previous conversation, it appears to be around 1 minute. For requests that may take up to 30 minutes, you'll need to use a third-party tool as a wrapper around Clay. Tools like Replit or Make can receive API requests, trigger Clay to process data, and return results once complete. This approach is recommended for situations where you need longer processing times than Clay's native timeout allows.
Is there any fallback URL where we can send the result of the API call in case the response takes longer than 1 minute?
Clay doesn't offer a native callback mechanism for API responses that exceed the timeout limit. For requests that may take longer than 1 minute, you'll need to implement a wrapper solution using third-party tools like Replit or Make that can handle extended processing times and manage the response delivery.