IF · OAuth Scopes

IF OAuth Scopes

OAuth 2.0 searched

IF publishes 11 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the IF API on a user’s behalf.

Tokens are issued from https://account.integrated.finance/auth/realms/ifp/protocol/openid-connect/token.

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.

CompanyFinancial ServicesEmbedded FinanceBanking as a ServicePaymentsCardsForeign ExchangeComplianceOpen BankingAPI

Scopes: 11 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://account.integrated.finance/auth/realms/ifp/protocol/openid-connect/token

Flows
clientCredentials

Scopes (11)

Scope	Description	Flows
openid	OpenID Connect authentication; required to receive an ID token.
api	Access to the Integrated Finance platform API surface.
profile	Basic profile claims for the authenticated subject.
email	Email address claim for the authenticated subject.
address	Address claim for the authenticated subject.
phone	Phone-number claim for the authenticated subject.
roles	Realm and client role memberships for the subject.
offline_access	Issue a refresh token for offline / long-lived access.
microprofile-jwt	MicroProfile JWT claims (groups, upn) for service-to-service tokens.
acr	Authentication Context Class Reference claim.
web-origins	Allowed CORS web origins for the client.

📄 Provider scope reference: https://developer.integrated.finance/docs/authentication

Source

OAuth Scopes

generated: '2026-07-19'
method: searched
source: well-known/if-openid-configuration.json
docs: https://developer.integrated.finance/docs/authentication
schemes:
- name: OAuth2
  source: https://account.integrated.finance/auth/realms/ifp/.well-known/openid-configuration
  flows:
  - flow: clientCredentials
    tokenUrl: https://account.integrated.finance/auth/realms/ifp/protocol/openid-connect/token
scopes:
- scope: openid
  description: OpenID Connect authentication; required to receive an ID token.
  sources: [well-known/if-openid-configuration.json]
- scope: api
  description: Access to the Integrated Finance platform API surface.
  sources: [well-known/if-openid-configuration.json]
- scope: profile
  description: Basic profile claims for the authenticated subject.
  sources: [well-known/if-openid-configuration.json]
- scope: email
  description: Email address claim for the authenticated subject.
  sources: [well-known/if-openid-configuration.json]
- scope: address
  description: Address claim for the authenticated subject.
  sources: [well-known/if-openid-configuration.json]
- scope: phone
  description: Phone-number claim for the authenticated subject.
  sources: [well-known/if-openid-configuration.json]
- scope: roles
  description: Realm and client role memberships for the subject.
  sources: [well-known/if-openid-configuration.json]
- scope: offline_access
  description: Issue a refresh token for offline / long-lived access.
  sources: [well-known/if-openid-configuration.json]
- scope: microprofile-jwt
  description: MicroProfile JWT claims (groups, upn) for service-to-service tokens.
  sources: [well-known/if-openid-configuration.json]
- scope: acr
  description: Authentication Context Class Reference claim.
  sources: [well-known/if-openid-configuration.json]
- scope: web-origins
  description: Allowed CORS web origins for the client.
  sources: [well-known/if-openid-configuration.json]
notes: >-
  Scopes are the Keycloak realm ("ifp") supported scopes read from the live OIDC
  discovery documents for the production and sandbox authorization servers. IF uses
  a client-credentials (service-account) model; per-resource authorization is
  carried by realm/client roles rather than fine-grained OAuth scopes.