Equifax · Rate Limits

Equifax Rate Limits

Equifax publishes NO numeric rate limit for any API product. The only limit statement on a public Equifax page is a warning that limits change without notice: consumers are told to expect that "rate limits applied to an API may change dynamically and may result in the API returning http status code 429". Quotas themselves are provisioned per customer, per product, at the credential level, and the production environment adds an IP allow-list on top. Sandbox and Test are documented as having no usage constraints at all. This replaces a 2026-05-04 bulk-sweep artifact that was written without a source; the numbers below are now sourced or honestly zero.

Equifax Rate Limits is the machine-readable rate-limit profile for Equifax on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring unpublished.

Limit state is signalled in the published, ratelimit_headers, retry_after, and note response headers, and an exhausted limit returns HTTP 429.

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

Tagged areas include Rate Limiting, Credit Bureau, Identity, and Fraud Prevention.

3 Limits Exhausted: HTTP 429 publishedratelimit_headersretry_afternote
Transcribed from the provider's documentation on 2026-09-06 — developer.equifax.com/documentation.
200, "url" => "https://developer.equifax.com/documentation"}" target="_blank" rel="noopener" class="btn btn-sm" style="background: #0891b2; color: white; margin-top: 0.75rem;">View Source
Rate LimitingCredit BureauIdentityFraud Prevention

Limits

Per-credentials negotiated limit api-credentials
unpublished
Provisioned per customer and per product under contract; no public number.
Sandbox environment sandbox-credentials
unpublished
Equifax states of Sandbox: "Currently there are no constraints." Of Test/UAT: "There are no usage constraints applied to our test APIs."
Live environment production-credentials
unpublished
"Usage constraints: Please contact your Equifax sales representative." Production additionally requires the calling gateway IP to be allow-listed; a non-allow-listed IP gets 403, not 429.

Policies

Dynamic limits
Equifax's published change policy tells consumers to build for limits that change without notification and to expect a 429 as a result.
Sandbox vs production
Use sandbox credentials for integration testing; production credentials require a Go Live review, an IP allow-list, and FCRA-permissible-purpose obligations.
Backoff
On 429 / 503, back off exponentially with jitter. Note that Equifax publishes no idempotency mechanism, so a retried inquiry is not a safe no-op — an Equifax credit inquiry posts to the consumer's file.

Sources

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.
All 92 tools →

Call it yourself

curl for this page
This rate limit
curl "https://apis.io/api/v1/rate-limits/equifax-rate-limits"
All rate limits
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.