Spinwheel · Rate Limits

Spinwheel Rate Limits

Spinwheel does not publish specific public rate limits for its embedded debt API. Limits are governed per partner under the production agreement and by the asynchronous, request-and-poll design of several operations (liability refresh and debt-profile pulls are submitted, then polled or delivered via webhook). Per-account and per-endpoint thresholds are not documented publicly and are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring requests and transactions.

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

Tagged areas include Fintech, Credit Data, Debt, Liabilities, and Payments.

4 Limits Throttle: 429
FintechCredit DataDebtLiabilitiesPaymentsEmbedded FinanceRate LimitingQuotasThrottling

Limits

Per-Partner API Limits account
requests
see provider documentation
Governed per partner under the production agreement; not publicly documented.
Credit Report / Debt Profile Pulls account
requests
see provider documentation
Equifax-backed pulls are metered per partner; submitted then delivered via poll/webhook.
Liability Refresh user
requests
see provider documentation
Refresh requests are submitted then polled via the refresh status endpoint or webhook.
Payments account
transactions
see provider documentation
Payment request throughput governed per partner agreement.

Policies

Asynchronous Poll / Webhook
Long-running operations (liability refresh, credit report pulls) are submitted and then completed asynchronously via polling the status endpoint or receiving a webhook event, rather than a single synchronous response.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor any Retry-After guidance on 429 responses.

Sources