Clarification Needed on Feature Timing for 4 Daily Runs

Thomas P. · 2025-02-27 14:34:01.376709+00

Hey following up on your recent feature announcement... Can we have more clarity on when it will run if I choose 4 times a day ? I have a few APIs that have cool of period usually by the hour so would be great to understand the timing

Clarification Needed on Feature Timing for 4 Daily Runs | Clay

6 comments

· Sorted by Oldest

Channeled
APP
·
·
We don't have specific information about the timing for running a feature 4 times a day. However, we can provide some general insights about managing API requests and rate limits in Clay. When using our HTTP API integration or other features that involve external APIs, you can set up rate limits to control how frequently requests are made. This can help manage cooldown periods for your APIs. You can specify a request limit and duration in milliseconds to spread out the requests over time. For example, if you want to run 4 times a day with hourly cooldowns, you could set a rate limit of 1 request per 21600000 ms (6 hours). This would space out the 4 daily runs evenly. To get more specific information about the timing of the feature you're referring to, could you please provide more details about which feature you're using? This will help me give you more accurate information.
Sources: HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University
Thomas P.
·
·
cc Romain L. Hélène B. Alba P.
Channeled
APP
·
·
We don't have specific information about the exact timing for running a feature 4 times a day. However, you can use our rate limiting feature to manage your API's cooldown period. To set this up: 1. Go to the rate limit section in your enrichment settings. 2. Set the Request Limit to 1. 3. Set the Duration to 21600000 ms (6 hours). This will space out the 4 daily runs evenly, respecting your hourly cooldown period. You can adjust these settings as needed to fit your specific API requirements. If you need more precise control or have further questions about this feature, please ask to speak with a human agent for personalized assistance.
Sources: HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University
Channeled
APP
·
·
Is that what you were looking for?
Channeled
APP
·
·
I'm glad I could help! Let me know if you have any other questions.
Channeled
APP
·
·
Thank you so much for sharing your feedback Thomas P.!

Loading comments

Channeled
APP
·
·
We don't have specific information about the timing for running a feature 4 times a day. However, we can provide some general insights about managing API requests and rate limits in Clay. When using our HTTP API integration or other features that involve external APIs, you can set up rate limits to control how frequently requests are made. This can help manage cooldown periods for your APIs. You can specify a request limit and duration in milliseconds to spread out the requests over time. For example, if you want to run 4 times a day with hourly cooldowns, you could set a rate limit of 1 request per 21600000 ms (6 hours). This would space out the 4 daily runs evenly. To get more specific information about the timing of the feature you're referring to, could you please provide more details about which feature you're using? This will help me give you more accurate information.
Sources: HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University
Thomas P.
·
·
cc Romain L. Hélène B. Alba P.
Channeled
APP
·
·
We don't have specific information about the exact timing for running a feature 4 times a day. However, you can use our rate limiting feature to manage your API's cooldown period. To set this up: 1. Go to the rate limit section in your enrichment settings. 2. Set the Request Limit to 1. 3. Set the Duration to 21600000 ms (6 hours). This will space out the 4 daily runs evenly, respecting your hourly cooldown period. You can adjust these settings as needed to fit your specific API requirements. If you need more precise control or have further questions about this feature, please ask to speak with a human agent for personalized assistance.
Sources: HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University
Channeled
APP
·
·
Is that what you were looking for?
Channeled
APP
·
·
I'm glad I could help! Let me know if you have any other questions.
Channeled
APP
·
·
Thank you so much for sharing your feedback Thomas P.!