generated: '2026-07-23'
method: searched
source: https://developer.triodos.com/docs/authorisation
docs: https://developer.triodos.com/docs/authorisation
notes: >-
  Scopes are documented in the Triodos authorisation guide, not in the OpenAPI
  securitySchemes (which the Berlin Group template leaves empty). Following
  NextGenPSD2, the resource scope is dynamic and bound to a specific consent or
  payment resource id, so access is scoped per-resource rather than per-tenant.
schemes:
- name: openid-connect
  flow: authorizationCode
  authorizationUrl: https://api.triodos.com/auth/{tenant}/v1/auth
  tokenUrl: https://api.triodos.com/auth/{tenant}/v1/token
scopes:
- scope: openid
  description: Standard OpenID Connect scope; always requested to start the SCA flow.
  flows: [authorizationCode]
- scope: offline_access
  description: >-
    Requests a refresh token for long-lived (recurring) account access. Added
    automatically to the scaRedirect link when recurring account access is
    requested.
  flows: [authorizationCode]
- scope: 'AIS:{consent-id}'
  description: >-
    Account Information Service access bound to a specific registered consent
    resource id (e.g. AIS:5e70106a-...). Grants read access to the accounts,
    balances, and transactions covered by that consent.
  flows: [authorizationCode]
- scope: 'PIS:{payment-id}'
  description: >-
    Payment Initiation Service authorisation bound to a specific payment resource
    id (e.g. PIS:5e70106a-...). Authorises execution of that single payment.
  flows: [authorizationCode]
- scope: 'PIIS:{consent-id}'
  description: >-
    Confirmation of Funds (CBPII/PIIS) access bound to a specific funds-
    confirmation consent resource id. Grants the right to query availability of
    funds on the covered account.
  flows: [authorizationCode]