Citizens Financial Group OAuth Scopes

OAuth 2.0 searched

Citizens Financial Group publishes 5 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the Citizens Financial Group API on a user’s behalf.

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.

BankingBuy Now Pay LaterFinancial-ServicesFDXLocatorOpen BankingPayments

Scopes: 5 Flows: Method: searched

Scopes (5)

Scope	Description	Flows
ir:read	Access to read Information Reporting data (account list, balances, transactions).	clientCredentials
av:read	Access to read Account Validation data.	clientCredentials
transfer:initiate	Access to initiate an internal account transfer.	clientCredentials
Payment:Initiate	Submit an RTP or ACH payment instruction.	clientCredentials
Payment:Query	Retrieve participant status and payment status.	clientCredentials

📄 Provider scope reference: https://developer.citizensbank.com/content/qut/CitizensPaymentAPIUserGuide.pdf

Source

OAuth Scopes

generated: '2026-09-05'
method: searched
source: >-
  Scope strings read from the harvested OpenAPI securitySchemes in openapi/ and from the sample token
  requests published in the Citizens API user guides (Payments v1.3, Account Transfer v1.0, Account
  Validation v1.6, Information Reporting v1.6).
docs: https://developer.citizensbank.com/content/qut/CitizensPaymentAPIUserGuide.pdf
provider: Citizens Financial Group
providerId: citizens-financial-group

authorization:
  flow: clientCredentials
  grant_type: client_credentials
  client_authentication: private_key_jwt over mTLS
  token_endpoint_production: https://apis.citizensbank.com/as/token.oauth2
  token_endpoint_sandbox: https://sandboxapis.citizensbank.com/as/token.oauth2
  note: >-
    Scopes are requested as a space-delimited `scope` form parameter on the token request. Citizens
    does not publish a consolidated scope reference page; the list below is the union of every scope
    string that appears in a published contract or a published sample request.

scopes:
  - scope: ir:read
    description: Access to read Information Reporting data (account list, balances, transactions).
    flows: [clientCredentials]
    evidence:
      - openapi/citizens-financial-group-information-reporting-openapi.yml
      - openapi/citizens-financial-group-payments-openapi.yml
      - https://developer.citizensbank.com/content/qut/CitizensInformationReportingAPIUserGuide.pdf
  - scope: av:read
    description: Access to read Account Validation data.
    flows: [clientCredentials]
    evidence:
      - openapi/citizens-financial-group-account-validation-openapi.yml
      - https://developer.citizensbank.com/content/qut/CitizensAccountValidationAPIUserGuide.pdf
  - scope: 'transfer:initiate'
    description: Access to initiate an internal account transfer.
    flows: [clientCredentials]
    evidence:
      - openapi/citizens-financial-group-account-transfer-openapi.yml
  - scope: 'Payment:Initiate'
    description: Submit an RTP or ACH payment instruction.
    flows: [clientCredentials]
    evidence:
      - https://developer.citizensbank.com/content/qut/CitizensPaymentAPIUserGuide.pdf
    note: >-
      Published only in the user guide's sample token request
      (--data 'scope=Payment:Initiate Payment:Query'); the Payments OpenAPI declares ir:read instead,
      which looks like a copy-paste carry-over from Information Reporting.
  - scope: 'Payment:Query'
    description: Retrieve participant status and payment status.
    flows: [clientCredentials]
    evidence:
      - https://developer.citizensbank.com/content/qut/CitizensPaymentAPIUserGuide.pdf

gaps:
  - >-
    The Payments OpenAPI's oauth2 scope map disagrees with the Payments user guide sample request
    (ir:read vs Payment:Initiate / Payment:Query). Recorded as published; not reconciled.
  - >-
    No scope reference page exists on developer.citizensbank.com. Scopes for the FDX Accounts /
    Statements surface and for Authorize are not published - those contracts declare header key
    schemes only.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com

Work with this as data

Every scope set 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 oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set 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 scope set

curl "https://apis.io/api/v1/scopes/citizens-financial-group-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?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.

GitHub Google LinkedIn

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