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.
Limits
Policies
Sources
- https://developer.freee.co.jp/
- https://developer.freee.co.jp/reference/accounting/reference
- https://github.com/freee/freee-api-schema
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/freee-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.