Fyle Rate Limits
Fyle does not publish fixed numeric per-account or per-endpoint rate limits for the Platform API in its public documentation. Throughput is governed primarily by pagination: every list endpoint requires offset, limit, and order query parameters, and the limit (page size) is capped by the server, so large reads are paged rather than pulled in a single request. Access tokens issued by the OAuth refresh-token grant are short-lived and must be refreshed, which naturally bounds sustained request rates. Clients that exceed platform limits should expect HTTP 429 responses and back off.
Fyle Rate Limits is the machine-readable rate-limit profile for Fyle on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests, records, and tokens.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled, unauthorized, and expiredToken.
Tagged areas include Expense Management, Spend Management, API, Rate Limiting, and Pagination.