Managing Apollo API Rate Limits for Efficient Data Retrieval | Clay

Managing Apollo API Rate Limits for Efficient Data Retrieval

So i ran a table of 5000 rows to get the company name from a company URL using the apollo API. THe problem is that the apollo API has a 200/minute rate limit. Is there a way to make the column run once every 1 minute so that I don’t have to rerun the column in batches of 200? I’m lookng at the clay HTTP module with limited success

6 comments

Channeled
APP
·
·
You can configure the rate limit settings for the Apollo API integration to handle your 5000 rows within the API limits: 1. In the API integration settings, locate the "Define rate limit" section 2. Set the Request Limit to 200 (matching Apollo's limit) 3. Set the Duration to 60000 milliseconds (60 seconds = 1 minute)This configuration will automatically pace the requests to stay within Apollo's rate limit of 200 requests per minute.If you continue experiencing rate limit issues, you can alternatively process your data in smaller batches of 200 rows at a time. Sources: HTTP API with JWT authentication | Documentation | Clay University Apollo.io integration overview | Documentation | Clay University
Channeled
APP
·
·
Did that answer your question?
John K.
·
·
where do I find the api integration settings. is that in clay?
Channeled
APP
·
·
For HTTP API integration settings in Clay: 1. Click your profile picture in the top-right corner 2. Go to Settings 3. Select the Connections tab in the sidebar 4. Click Add Connection to set up a new integrationFor the Apollo API specifically, you'll need to configure the HTTP API integration when creating your enrichment column: 1. Select HTTP API from the Enrichment Panel 2. Choose your HTTP method (GET, POST, PUT, or DELETE) 3. Define your API endpoint 4. Configure any necessary parameters Sources: Managing integration accounts | Documentation | Clay University HTTP API integration overview | Documentation | Clay University
Channeled
APP
·
·
Is that what you were looking for?
Channeled
APP
·
·
Hi John K.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: