Method Financial · Rate Limits

Method Fi Rate Limits

The Method API enforces per-account rate limits to protect platform stability. Requests that exceed the allowed rate receive an HTTP 429 response and should be retried with exponential backoff. Method also supports idempotency keys and request IDs for safe retries. Specific per-endpoint request-per-minute thresholds are not publicly published and are not reconciled in this artifact.

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

It captures 3 rate-limit definitions, measuring requests.

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

Tagged areas include FinTech, Payments, Liabilities, Debt, and Embedded Finance.

3 Limits Throttle: 429
FinTechPaymentsLiabilitiesDebtEmbedded FinanceRate LimitingQuotasThrottling

Limits

Requests Per Minute account
requests
see provider documentation
Per-account request rate; exceeding returns HTTP 429.
Data Refresh Concurrency account
requests
see provider documentation
Balances, payoffs, transactions, and attribute refreshes may have separate concurrency limits.
Connect Requests account
requests
see provider documentation
Liability discovery requests may be throttled separately from CRUD endpoints.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Idempotency
Send an Idempotency-Key header on writes so retries do not duplicate entities, accounts, or payments.
Request IDs
Each response carries a request ID for support and debugging of throttled or failed calls.

Sources