freee · Rate Limits

Freee Rate Limits

freee applies per-endpoint access control rather than publishing a single fixed numeric request-rate ceiling for every operation. When freee detects excessive access to an endpoint within a period it returns HTTP 429 (Too Many Requests) and includes rate-limit headers on the response (x-ratelimit-limit, x-ratelimit-remaining, and x-ratelimit-reset with a reset timestamp). freee may also return HTTP 403 when it detects sustained excessive access, with access typically restored after roughly 10 minutes. Every response also carries an X-Freee-Request-ID header useful for support and debugging.

Freee Rate Limits is the machine-readable rate-limit profile for freee on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and blocked.

Tagged areas include Accounting, HR, Payroll, Rate Limiting, and Quotas.

2 Limits Throttle: 429
AccountingHRPayrollRate LimitingQuotasJapan

Limits

Per-Endpoint Request Rate application-endpoint
requests
enforced (numeric limit surfaced via x-ratelimit-limit header)
freee throttles high-frequency access per endpoint and returns 429 with x-ratelimit-* headers.
Sustained Excessive Access application
requests
blocked with 403
Prolonged excessive access can return 403; access is typically restored after ~10 minutes.

Policies

Backoff Strategy
On 429, honor the x-ratelimit-reset timestamp and retry after it passes; use exponential backoff with jitter. On 403 due to throttling, pause for roughly 10 minutes before retrying.
Request Correlation
Log the X-Freee-Request-ID from each response to correlate failures with freee support.
Incremental Polling
freee has no push transport; poll incrementally using date-range filters (for example start/end update dates on partners or wallet_txns) to minimize request volume.

Sources