Datplan guide
API Rate Limits Explained: Why Your Accounting Data Does Not Always Sync
Understand API rate limits, provider allowances, tenant usage and why accounting data syncs may stop before a reporting tier allowance is fully used.
What is an API rate limit?
An API rate limit is a rule set by the source provider that controls how many requests, calls or data operations can happen within a period. Providers use limits to protect their systems, manage fair use and keep services stable for all customers.
A reporting tool can have its own allowance, but it cannot override the provider’s limits. If the provider slows or blocks requests, the sync may need to wait, retry later or stop with a status message.
Why a sync may stop before a Datplan allowance is reached
Datplan plans include source-tier allowances such as monthly data allowance and pull credits. Those are Datplan limits. They sit alongside provider-side limits.
If another app, integration, automation or user consumes the same provider tenant’s API quota, Datplan may be limited before the Datplan tier allowance is fully used. This is why tier tables include source-provider caveats.
Full pulls and incremental pulls
A full pull asks for a wider rebuild of source data. It can be useful when data is stale, incomplete or support advises a rebuild. It may use more allowance because more source data is requested.
An incremental pull uses the last saved pull position or checkpoint where supported by the provider and endpoint. This can reduce repeated full pulls and help preserve both Datplan tier allowance and provider allowance.
What users should check first
If a sync does not produce the expected result, start with the visible sync status, endpoint results, last sync information and usage page. Then check whether another integration is using the same provider account and whether the source provider is experiencing availability or rate-limit issues.
Avoid repeatedly running full re-pulls without a reason. Standard syncs and incremental pulls are usually better for routine reporting where they are supported.
How Datplan helps users understand sync state
Datplan DataPull is designed to show source-level usage and sync status so users can see what happened. This matters because accounting reporting depends on knowing whether the data is fresh, partial, delayed or blocked by a provider-side condition.
A good reporting workflow should not hide these limits. It should make them visible enough for accountants, consultants and finance teams to act on them.
Questions this guide answers
Can Datplan bypass provider limits?
No. Datplan does not own or control the provider API and cannot bypass provider rate limits, tenant allowances or service availability rules.
Do incremental pulls always work?
No. Incremental behaviour depends on the source provider, endpoint and available checkpoint data.