generated: '2026-09-06'
method: searched
source: https://developer.equifax.com/documentation
docs: https://developer.equifax.com/documentation
provider: Equifax
providerId: equifax
flow: clientCredentials
token_endpoint: https://api.equifax.com/v2/oauth/token
scope_count: 0
scopes: []
note: >-
  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.
gated: true
gate: Equifax Developer Portal sign-in (https://developer.equifax.com/user/login)
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com