FIS Global · OAuth Scopes
FIS Global OAuth Scopes
OAuth 2.0
searched
FIS Global 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.
BankingCore BankingFinancial ServicesPaymentsFintech
Scopes: 0
Flows:
Method: searched
Scopes (0)
FIS Global 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.
FIS publishes no OAuth scope surface that a member of the public can read. The one public contract, FIS Accounting Data as a Service, authenticates with an opaque bearer token minted from a Basic-auth key pair — it declares no oauth2 securityScheme and no scopes, so there is nothing to enumerate. FIS Code Connect generates client keys behind a reviewed registration; whatever scope model it uses is not visible without an account.
FIS publishes no OAuth scope surface that a member of the public can read. The one public contract, FIS Accounting Data as a Service, authenticates with an opaque bearer token minted from a Basic-auth key pair — it declares no oauth2 securityScheme and no scopes, so there is nothing to enumerate. FIS Code Connect generates client keys behind a reviewed registration; whatever scope model it uses is not visible without an account.
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.