C. Hoare & Co. · OAuth Scopes

C. Hoare & Co. OAuth Scopes

OAuth 2.0 derived

C. Hoare & Co. publishes 2 OAuth 2.0 scopes via the authorizationCode and clientCredentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the C. Hoare & Co. API on a user’s behalf.

Tokens are issued from https://authserver.example/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.

Financial ServicesBankingPrivate BankOpen BankingPSD2OBIEFAPIUnited KingdomPaymentsAccount Information

Scopes: 2 Flows: authorizationCode, clientCredentials Method: derived

OAuth endpoints

Authorization URL
https://authserver.example/authorization

Token URL
https://authserver.example/token

Flows
authorizationCodeclientCredentials

Scopes (2)

Scope	Description	Flows
accounts	Ability to read Accounts information	authorizationCode, clientCredentials
payments	Generic payment scope	authorizationCode, clientCredentials

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-23'
method: derived
source: openapi/c-hoare-and-co-account-and-transaction-api-openapi.yml, openapi/c-hoare-and-co-dynamic-client-registration-api-openapi.yml,
  openapi/c-hoare-and-co-payment-initiation-api-openapi.yml
schemes:
- name: PSUOAuth2Security
  source: openapi/c-hoare-and-co-account-and-transaction-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://authserver.example/authorization
    tokenUrl: https://authserver.example/token
  description: OAuth flow, it is required when the PSU needs to perform SCA with the ASPSP when
    a TPP wants to access an ASPSP resource owned by the PSU
- name: TPPOAuth2Security
  source: openapi/c-hoare-and-co-account-and-transaction-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://authserver.example/token
  description: TPP client credential authorisation flow with the ASPSP
- name: TPPOAuth2Security
  source: openapi/c-hoare-and-co-dynamic-client-registration-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://authserver.example/token
  description: TPP client credential authorisation flow with the ASPSP. No scopes defined as
    per specification
- name: PSUOAuth2Security
  source: openapi/c-hoare-and-co-payment-initiation-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://authserver.example/authorization
    tokenUrl: https://authserver.example/token
  description: OAuth flow, it is required when the PSU needs to perform SCA with the ASPSP when
    a TPP wants to access an ASPSP resource owned by the PSU
- name: TPPOAuth2Security
  source: openapi/c-hoare-and-co-payment-initiation-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://authserver.example/token
  description: TPP client credential authorisation flow with the ASPSP
scopes:
- scope: accounts
  description: Ability to read Accounts information
  flows:
  - authorizationCode
  - clientCredentials
  sources:
  - openapi/c-hoare-and-co-account-and-transaction-api-openapi.yml
- scope: payments
  description: Generic payment scope
  flows:
  - authorizationCode
  - clientCredentials
  sources:
  - openapi/c-hoare-and-co-payment-initiation-api-openapi.yml