Method enforces rate limits on all API requests to protect platform stability and ensure fair usage across all customers. Rate limits apply to all environments (Development, Sandbox, and Production) and all API versions.Documentation Index
Fetch the complete documentation index at: https://docs.methodfi.com/llms.txt
Use this file to discover all available pages before exploring further.
How rate limits work
Requests are counted per API key within a 60-second rolling window. Limits are applied across multiple tiers based on operation type — more sensitive operations (such as payment creation) have stricter limits, while high-volume read and write operations have more generous allowances. Each tier tracks its own counter independently, so usage against one tier does not affect your capacity in another. When a rate limit is exceeded, requests matching that tier are blocked for 60 seconds, after which requests are automatically accepted again.The same rate limits apply across all environments (Development, Sandbox, and Production).
Rate limits encountered during testing in Development or Sandbox reflect the same thresholds
your integration will experience in Production.
Rate limit response
When rate limited, the API returns an HTTP429 status code with the following response body:
Handling rate limits
When you receive a429 response, the block lasts for 60 seconds. Retrying immediately
will not succeed. We recommend waiting at least 60 seconds before retrying, then using
exponential backoff if subsequent attempts are still rate limited.
Combine rate limit retries with idempotency keys on POST requests to
ensure retried requests are not processed more than once.