Hi,

Rate limit increases require a paid upgrade to your plan. Before suggesting a rate limit increase, I recommend looking at the logic of this batch job. We may be able to work together here to create better API efficiency and reduce the number of calls needed. 

A couple of suggestions that could really help here:

1.  Running the job hourly instead of once in the evening might be more effective. If the company only needs to run it once daily, it seems like it's a background job, so speed isn't important. I would suggest that you process the data a little slower (serial rather than parallel), and ensure rate limit headers are being respected by easing requests when you approach the rate limit. You should try to proactively try to avoid hitting the rate limit rather than seeing how far you can push the system.

2. Do you have the ability or means to cache this data on a daily basis? For instance, if you could fetch all company, team, or teammate contacts, it may allow you to  cut 1-3 calls per contact just by having the information available to parse, rather than fetch each one. 

--Justin