Calls to our API are limited to 2500 per day per organization account to avoid abuse or negligent integrations that degrade platform performance.
API limits are reset upon the first API request made after midnight in the time zone specified on your Organization Setup page.
We also have a soft limit of 3 concurrent API connections per organization account.
Don’t hesitate to contact our support team if these limits pose a problem for your application.
Actions that do not count towards API limits
- All connector actions, such as form connectors, data source connectors, etc, are not counted.
- GET requests to download files from our File APIs
- All interactions between our platform and your app
Checking your API usage
We provide a daily log of API usage per account for API Calls Today and Last API Call.
Go to Organization & Users > Organization Setup > Integrations – Info box on the right.



Click the “View Logs” link for details on the last 250 calls.
Ways that you can reduce API calls
Increase time between calls
The most straightforward way is to increase the time between repetitive/polling API calls you make.
For example, if you update a Data Source every 5 minutes, try changing it to once every 10 minutes—this would halve the average number of API calls you make per day.
Remove Unnecessary API Calls
Check whether you have any API calls that could be removed altogether from your processing.
For example, if you push Data Source changes to our platform, your system is expected to be the “source of truth.” So if your code was making an API call to check the size of the Data Source on our side, this is probably unnecessary and could be removed.
Insert and delete in one call
You can issue incremental inserts and deletes in one API call on the Data Source API.
So, if deletions need to be made, they can be sent in the same API call as a set of inserts, possibly saving a few API calls.
Platform Sync Data Source Connector
Have you considered using a Platform Sync connector on your data sources?
Platform Sync means the app connects directly to a web service you define. This bypasses our platform for retrieving rows, so you don’t need to push any rows to us.
An added benefit is that you can identify who the user is as well, so you can filter rows on your side as part of your response to the app directly.
Plus, you get “on-demand pull” from the app rather than needing to use some time interval for updating the rows, since the app will check in with your web service every time it synchronizes.
The Platform Sync API is very similar to the existing Data Source API that you are using, so it might not require a significant code change. Even if you moved a few of your most actively changing data sources to use this approach, that could solve the API limit problem.
If you’d like to know more about this, contact our support team for help or information.