Equifax · OAuth Scopes
Equifax OAuth Scopes
OAuth 2.0
searched
Equifax uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
CreditCredit HistoryCredit ReportingIdentityFraud DetectionFortune 1000
Scopes: 0
Flows:
Method: searched
Scopes (0)
Equifax implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.
Equifax documents that a `scope` parameter is REQUIRED in the OAuth 2.0 client_credentials token request ("you obtain the Access Token by providing only the client_id, client_secret, and the scope"), but publishes no scope reference. Scope values are per-API-product and are rendered only on the signed-in application page in the Equifax Developer Portal — the public quick-start guide instructs integrators to "Expand each API to confirm the appropriate endpoint 'Scope' to use in test mode" (https://assets.equifax.com/marketing/US/assets/developer-quick-start-guide.PDF). scope_count is an honest zero: zero scope values are published, not zero scopes exist. Recovering the real list requires an authenticated portal session, which this pipeline does not create.
Equifax documents that a `scope` parameter is REQUIRED in the OAuth 2.0 client_credentials token request ("you obtain the Access Token by providing only the client_id, client_secret, and the scope"), but publishes no scope reference. Scope values are per-API-product and are rendered only on the signed-in application page in the Equifax Developer Portal — the public quick-start guide instructs integrators to "Expand each API to confirm the appropriate endpoint 'Scope' to use in test mode" (https://assets.equifax.com/marketing/US/assets/developer-quick-start-guide.PDF). scope_count is an honest zero: zero scope values are published, not zero scopes exist. Recovering the real list requires an authenticated portal session, which this pipeline does not create.
📄 Provider scope reference: https://developer.equifax.com/documentation
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.