We are working on a batch pull system to help us edit/curate pulled active.com events before re-upload to our server
We are concerned that a batch pull could exceed the API server call limit. We are filtering by keyword, state, zip, and date range, but could pull hundreds of events in a single batch.
Are there any tips or methods we can user to avoid this potential issue?
We are looking into this and I hope you have some insight for you soon regarding the server call limit.
Thanks,
Jessica
Jessica B
–
13 years ago
Hello Dan,
We can increase your api request limit some, but you will probably need to spread the import over several days.
I do not know how many keyword and date range variations you are planning, but there are potentially 43,000 US zip codes. Assuming you do 2 date ranges and 3 different keywords, that is (43,000 * 2 * 3 =) 258,000 calls to search.
Can you do some analysis to see how many you would ideally want? We can probably meet you in the middle somewhere.
Some recommendations -
Reduce the number of location queries (popular zip codes, cities) Set the 'num' parameter to 100 to get the most results per page Do not query for multiple date ranges, search for all future events (m=meta:endDate:daterange:today..)
We are working on a batch pull system to help us edit/curate pulled active.com events before re-upload to our server
We are concerned that a batch pull could exceed the API server call limit. We are filtering by keyword, state, zip, and date range, but could pull hundreds of events in a single batch.
Are there any tips or methods we can user to avoid this potential issue?
Message edited by Dan Tashman 13 years ago
Tags
Jessica B – 13 years ago
Hello Dan,
We are looking into this and I hope you have some insight for you soon regarding the server call limit.
Thanks, Jessica
Jessica B – 13 years ago
Hello Dan,
We can increase your api request limit some, but you will probably need to spread the import over several days.
I do not know how many keyword and date range variations you are planning, but there are potentially 43,000 US zip codes. Assuming you do 2 date ranges and 3 different keywords, that is (43,000 * 2 * 3 =) 258,000 calls to search.
Can you do some analysis to see how many you would ideally want? We can probably meet you in the middle somewhere.
Some recommendations - Reduce the number of location queries (popular zip codes, cities) Set the 'num' parameter to 100 to get the most results per page Do not query for multiple date ranges, search for all future events (m=meta:endDate:daterange:today..)
Thanks so much and I hope this was helpful.
Jessica