Compounding API calls
The number one cause of hitting the [API throttling limit](/kb/apithrottlinglimitreachedexception?api=zohocrm) is compounding API calls. This occurs when an endpoint has an associated subset that requires a large number of calls to be made in order to acquire its data. So whenever the parent endpoint syncs it uses up a significant portion of your daily API call limit, often causing the limit to be hit with only a limited portion of your data pulled down.
## What to do
If you don't need to report on these subsets then they can be deactivated to avoid the extra load. SyncHub puts a warning label on any subset that is at risk of this behaviour. We recommend you deactivate all subsets carrying this warning unless you are sure you need to report on them. Be aware you do need to be in [nerd mode](/kb/displaymode?api=zohocrm) in order to see the warning.
If you do need to report on these subsets and you are finding that you are hitting your call limit too often then you can manage the situation by staging your endpoints to run consecutively rather than all at once. You should also follow all the [usual steps](/kb/importingyourhistoricaldata?api=zohocrm) to efficiently backdate your historical data.
#### Read more about this on our [blog](https://blog.synchub.io/articles/compounding-api-calls)