Qwist Strong Customer Authentication API

openapi: 3.2.0
info:
  title: nrich Strong Customer Authentication API
  version: '2.10'
  contact:
    name: Qwist GmbH
    email: partnersupport@qwist.com
    url: https://qwist.com
  description: This is the reference for Qwist's nrich API
servers:
- url: https://api.nrich.qwist.cloud
  description: Staging environment
tags:
- name: Strong Customer Authentication
paths:
  /rest/accesses/{access-id}/syncs/{sync-id}/challenges:
    get:
      summary: List synchronization challenges
      operationId: listSyncChallenges
      tags:
      - Strong Customer Authentication
      parameters:
      - $ref: '#/paths/~1rest~1accesses~1{access-id}/get/parameters/0'
      - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}/get/parameters/1'
      security:
      - user_auth: []
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}/get/responses/200/content/application~1json/schema'
        '400':
          $ref: '#/paths/~1rest~1user/put/responses/400'
        '401':
          $ref: '#/paths/~1catalog/get/responses/401'
  /rest/accesses/{access-id}/syncs/{sync-id}/challenges/{challenge-id}:
    get:
      summary: Get synchronization challenge
      operationId: getSyncChallenge
      tags:
      - Strong Customer Authentication
      parameters:
      - $ref: '#/paths/~1rest~1accesses~1{access-id}/get/parameters/0'
      - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}/get/parameters/1'
      - name: challenge-id
        in: path
        required: true
        schema:
          type: string
          example: aa15bc06-3d89-48ce-9e21-5094f0443046.3
          description: nrich ID of the challenge.
      security:
      - user_auth: []
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                oneOf:
                - allOf:
                  - type: object
                    properties:
                      id:
                        $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}/get/parameters/2/schema'
                      created_at:
                        $ref: '#/paths/~1uploads/post/responses/200/content/application~1json/schema/properties/ended_at'
                        description: Time at which the challenge was created.
                        example: '2019-08-31T12:13:11.000Z'
                    required:
                    - id
                    - created_at
                  - type: object
                    properties:
                      type:
                        type: string
                        enum:
                        - METHOD_SELECTION
                      auth_methods:
                        type: array
                        items:
                          $ref: '#/paths/~1rest~1accesses/get/responses/200/content/application~1json/schema/items/properties/auth_methods/items'
                    required:
                    - type
                    - auth_methods
                - allOf:
                  - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}/get/responses/200/content/application~1json/schema/oneOf/0/allOf/0'
                  - type: object
                    properties:
                      type:
                        type: string
                        enum:
                        - MEDIUM_SELECTION
                      auth_media:
                        type: array
                        items:
                          type: object
                          properties:
                            id:
                              $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}~1response/post/requestBody/content/application~1json/schema/oneOf/1/properties/medium_id'
                            name:
                              type: string
                              description: A name to identify the device or app.
                            active:
                              type: boolean
                              description: Indicates if this medium has been reported active by the financial provider.
                          required:
                          - id
                          - name
                          - active
                    required:
                    - type
                    - auth_media
                - allOf:
                  - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}/get/responses/200/content/application~1json/schema/oneOf/0/allOf/0'
                  - type: object
                    properties:
                      type:
                        type: string
                        enum:
                        - EMBEDDED
                      format:
                        type: string
                        description: Indicates how the `data` field should be interpreted.
                        enum:
                        - PHOTO
                        - HHD
                        - TEXT
                        - HTML
                      version:
                        type: string
                        description: The version of the used challenge type. Left empty if it does not apply.
                      data:
                        type: string
                        description: The format of the data is specified in the `format` field.
                      additional_info:
                        type: string
                        description: Provides additional information text to be displayed to the end-user.
                      label:
                        type: string
                        description: To be used as label for the user input field in UIs.
                      input_format:
                        type: string
                        enum:
                        - STRING
                        - INTEGER
                        description: The expected input format or type for the response to the challenge.
                      max_length:
                        type: integer
                        description: Maximum length of the response to be provided to the challenge.
                      min_length:
                        type: integer
                        description: Minimum length of the response to be provided to the challenge.
                    required:
                    - type
                    - label
                    - format
                    - data
                - allOf:
                  - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}/get/responses/200/content/application~1json/schema/oneOf/0/allOf/0'
                  - type: object
                    properties:
                      type:
                        type: string
                        enum:
                        - REDIRECT
                      location:
                        $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs/post/requestBody/content/application~1json/schema/properties/redirect_uri'
                        description: The location the user should be directed to.
                    required:
                    - type
                    - location
                - allOf:
                  - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}/get/responses/200/content/application~1json/schema/oneOf/0/allOf/0'
                  - type: object
                    properties:
                      id:
                        $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}/get/parameters/2/schema'
                      type:
                        type: string
                        enum:
                        - DECOUPLED
                      message:
                        type: string
                        description: Instructional text to be displayed to the end-user.
                    required:
                    - id
                    - type
                    - message
        '400':
          $ref: '#/paths/~1rest~1user/put/responses/400'
        '401':
          $ref: '#/paths/~1catalog/get/responses/401'
  /rest/accesses/{access-id}/syncs/{sync-id}/challenges/{challenge-id}/response:
    post:
      summary: Solve synchronization challenge
      description: This endpoint is used to answer an authorization challenge that was issued by the financial provider. In addition to the normal transport layer encryption it is possible to encrypt the challenge response using JSON web encryption. Note that a challenge can only be answered once. Subsequent submission of a response to the same challenge will result in an error (HTTP status `409`).
      operationId: solveSyncChallenge
      tags:
      - Strong Customer Authentication
      parameters:
      - $ref: '#/paths/~1rest~1accesses~1{access-id}/get/parameters/0'
      - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}/get/parameters/1'
      - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}/get/parameters/2'
      security:
      - user_auth: []
      requestBody:
        content:
          application/json:
            schema:
              oneOf:
              - type: object
                properties:
                  method_id:
                    type: string
                    example: M12345.6
                    description: nrich ID of SCA method.
              - type: object
                properties:
                  medium_id:
                    type: string
                    example: D12345.6
                    description: nrich ID of SCA medium.
              - type: object
                properties:
                  value:
                    type: string
                    example: '111111'
                    description: Response to the auth challenge. The source of the value depends on the selected authentication method.
              - type: object
                properties:
                  type:
                    type: string
                    description: The type of the `value`. Always set to the value `"encrypted"`.
                    enum:
                    - encrypted
                  value:
                    type: string
                    example: eyJhbGciOiJSU0EtT0FFUCIsImVuYyI6IkEyNTZDQkMtSFM1MTIifQ.EdCMnSp7M_0UQEe5mPGuQtNf3hcaPcjQ3tbmfEkjV5wa-6mZMnhCD6Zq0U0anft4iuaBLQha-EAflD-7D2Wl6MfZeFYka_TC9flrV-av-cxDvzP2r4Cj_YedmBj3EOLawz4YRo_s65dX7hvwsdd--uOxXbdx-UXYLvDxykh8E1M1mfjdLFwpeGgVILPhJeURMglWttovrB22cEV8UASNHV7dDfvyqKIfYfecxCqKvr-D6bnyZf6w-Jp49GLNCXz9e6ZgDD521Z_Ci_-bBEwbQdIUkNLuGtFLKUuiv1oMinBzwOrAlREL1zOnem06olXpcSCZE_Esto80ISWHOW0k3w.-0imErCMK7ahidc0d0ivwg.K4_6p6qT6W7jILdLjeZMww.slCawx18gWmPRCSPWOePC46OcweOve_B7DA0Kj6Wkdk
                    description: '[JWE encrypted](#section/JWE-encryption) auth challenge response.'
      responses:
        '202':
          description: Accepted.
        '400':
          $ref: '#/paths/~1rest~1user/put/responses/400'
        '401':
          $ref: '#/paths/~1catalog/get/responses/401'
        '409':
          description: Conflicting resource state.
          content:
            application/json:
              schema:
                $ref: '#/paths/~1catalog/get/responses/401/content/application~1json/schema'
              example:
                error:
                  code: 1006
                  group: client
                  data: {}
                  description: Unprocessable entity.
  /rest/accounts/{account-id}/payments/{payment-id}/init/{init-id}/challenges:
    get:
      summary: List payment challenges of account
      deprecated: true
      operationId: listPaymentChallengesOfAccount
      description: '**Deprecated** in favour of list payment challenges endpoint.'
      tags:
      - Strong Customer Authentication
      parameters:
      - $ref: '#/paths/~1rest~1accounts~1{account-id}/get/parameters/0'
      - $ref: '#/paths/~1rest~1payments~1{payment-id}~1init/post/parameters/0'
      - $ref: '#/paths/~1rest~1payments~1{payment-id}~1init~1{init-id}/get/parameters/1'
      security:
      - user_auth: []
      responses:
        '200':
          $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges/get/responses/200'
        '400':
          $ref: '#/paths/~1rest~1user/put/responses/400'
        '401':
          $ref: '#/paths/~1catalog/get/responses/401'
  /rest/accounts/{account-id}/payments/{payment-id}/init/{init-id}/challenges/{challenge-id}:
    get:
      summary: Get payment challenge of account
      deprecated: true
      operationId: getPaymentChallengeOfAccount
      description: '**Deprecated** in favour of payment challenge details endpoint.'
      tags:
      - Strong Customer Authentication
      parameters:
      - $ref: '#/paths/~1rest~1accounts~1{account-id}/get/parameters/0'
      - $ref: '#/paths/~1rest~1payments~1{payment-id}~1init/post/parameters/0'
      - $ref: '#/paths/~1rest~1payments~1{payment-id}~1init~1{init-id}/get/parameters/1'
      - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}/get/parameters/2'
      security:
      - user_auth: []
      responses:
        '200':
          $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}/get/responses/200'
        '400':
          $ref: '#/paths/~1rest~1user/put/responses/400'
        '401':
          $ref: '#/paths/~1catalog/get/responses/401'
  /rest/accounts/{account-id}/payments/{payment-id}/init/{init-id}/challenges/{challenge-id}/response:
    post:
      summary: Solve payment challenge of account
      deprecated: true
      operationId: solvePaymentChallengeOfAccount
      description: 'This endpoint is used to answer an authorization challenge that was issued by the financial provider. In addition to the normal transport layer encryption it is possible to encrypt the challenge response using JSON web encryption. Note that a challenge can only be answered once. Subsequent submission of a response to the same challenge will result in an error.

        **Deprecated** in favour of payment challenge response endpoint.'
      tags:
      - Strong Customer Authentication
      parameters:
      - $ref: '#/paths/~1rest~1accounts~1{account-id}/get/parameters/0'
      - $ref: '#/paths/~1rest~1payments~1{payment-id}~1init/post/parameters/0'
      - $ref: '#/paths/~1rest~1payments~1{payment-id}~1init~1{init-id}/get/parameters/1'
      - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}/get/parameters/2'
      security:
      - user_auth: []
      requestBody:
        content:
          application/json:
            schema:
              oneOf:
              - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}~1response/post/requestBody/content/application~1json/schema/oneOf/0'
              - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}~1response/post/requestBody/content/application~1json/schema/oneOf/1'
              - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}~1response/post/requestBody/content/application~1json/schema/oneOf/2'
              - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}~1response/post/requestBody/content/application~1json/schema/oneOf/3'
      responses:
        '202':
          $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}~1response/post/responses/202'
        '400':
          $ref: '#/paths/~1rest~1user/put/responses/400'
        '401':
          $ref: '#/paths/~1catalog/get/responses/401'
        '409':
          $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}~1response/post/responses/409'
  /rest/payments/{payment-id}/init/{init-id}/challenges:
    get:
      summary: List payment challenges
      operationId: listPaymentChallenges
      tags:
      - Strong Customer Authentication
      parameters:
      - $ref: '#/paths/~1rest~1payments~1{payment-id}~1init/post/parameters/0'
      - $ref: '#/paths/~1rest~1payments~1{payment-id}~1init~1{init-id}/get/parameters/1'
      security:
      - user_auth: []
      - client_auth: []
      responses:
        '200':
          $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges/get/responses/200'
        '400':
          $ref: '#/paths/~1rest~1user/put/responses/400'
        '401':
          $ref: '#/paths/~1catalog/get/responses/401'
  /rest/payments/{payment-id}/init/{init-id}/challenges/{challenge-id}:
    get:
      summary: Get payment challenge
      operationId: getPaymentChallenge
      tags:
      - Strong Customer Authentication
      parameters:
      - $ref: '#/paths/~1rest~1payments~1{payment-id}~1init/post/parameters/0'
      - $ref: '#/paths/~1rest~1payments~1{payment-id}~1init~1{init-id}/get/parameters/1'
      - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}/get/parameters/2'
      security:
      - user_auth: []
      - client_auth: []
      responses:
        '200':
          $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}/get/responses/200'
        '400':
          $ref: '#/paths/~1rest~1user/put/responses/400'
        '401':
          $ref: '#/paths/~1catalog/get/responses/401'
  /rest/payments/{payment-id}/init/{init-id}/challenges/{challenge-id}/response:
    post:
      summary: Solve payment challenge
      description: This endpoint is used to answer an authorization challenge that was issued by the financial provider. In addition to the normal transport layer encryption it is possible to encrypt the challenge response using JSON web encryption. Note that a challenge can only be answered once. Subsequent submission of a response to the same challenge will result in an error.
      operationId: solvePaymentChallenge
      tags:
      - Strong Customer Authentication
      parameters:
      - $ref: '#/paths/~1rest~1payments~1{payment-id}~1init/post/parameters/0'
      - $ref: '#/paths/~1rest~1payments~1{payment-id}~1init~1{init-id}/get/parameters/1'
      - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}/get/parameters/2'
      security:
      - user_auth: []
      - client_auth: []
      requestBody:
        content:
          application/json:
            schema:
              oneOf:
              - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}~1response/post/requestBody/content/application~1json/schema/oneOf/0'
              - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}~1response/post/requestBody/content/application~1json/schema/oneOf/1'
              - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}~1response/post/requestBody/content/application~1json/schema/oneOf/2'
              - $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}~1response/post/requestBody/content/application~1json/schema/oneOf/3'
      responses:
        '202':
          $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}~1response/post/responses/202'
        '400':
          $ref: '#/paths/~1rest~1user/put/responses/400'
        '401':
          $ref: '#/paths/~1catalog/get/responses/401'
        '409':
          $ref: '#/paths/~1rest~1accesses~1{access-id}~1syncs~1{sync-id}~1challenges~1{challenge-id}~1response/post/responses/409'
components:
  securitySchemes:
    user_auth:
      type: http
      description: 'In order to access any information belonging to a user, a client has to authenticate with a token linking itself to the user.  This token is called an `access token` and contains information on the client, the user and the level of access the client has to the users data. In order to authenticate using such an access token the HTTP header `Authorization` is set to `Bearer <access token>`. The  `access token` is formatted

        as a JSON Web Token according to [RFC7519](https://tools.ietf.org/html/rfc7519)


        Such an `access token` is either returned when


        * exchanging an authorization code after a successful OAuth login flow

        * logging in with the user''s credentials

        * exchanging a refresh token, which is returned at either of the aforementioned points


        **Authentication errors**


        In case of an authentication error a HTTP code 401 response is returned containing further

        details on the kind of error in the `WWW-Authenticate` header.


        In addition to the below listed scope the flags are used for simple boolean permissions.


        | Flag            | Description                                  |

        | --              | --                                           |

        | submit_payments | Allow submission of payments to bank server  |

        | offline         | Access finX API when the user is not present |

        | create_user     | Allow creation of finX accounts              |


        **Example**


        The string `"accounts=rw submit_payments"` is URL-encoded and passed as the URL

        parameter `scope`.'
      scheme: bearer
      bearerFormat: JWT
      x-bearerInfoFunc: app.decode_token
      x-scopes:
        accounts=rw: Modify accounts
        accounts=ro: Read accounts
        balance=ro: Read account balance
        securities=ro: Read securities
        transactions=ro: Read transactions
        transactions=rw: Modify transactions
        payments=ro: Read payments
        payments=rw: Create/modify payments
        submit_payments: Submit payment to service provider
        user=ro: Read user information
        user=rw: Modify user information
    client_auth:
      x-basicInfoFunc: app.basic_auth
      type: http
      scheme: basic
      description: Client authentication is performed via [HTTP Basic Auth](https://en.wikipedia.org/wiki/Basic_access_authentication) with client ID as username and client secret as password.
x-provenance:
  method: searched
  source: https://docs.qwist.com/reference
  harvested: '2026-10-21'
  tool: harvest-readme-openapi.py
  note: Assembled verbatim from the OpenAPI definition ReadMe embeds in each operation page of the provider's developer portal; paths and components merged by API title, nothing authored.
  assembled_from:
  - https://docs.qwist.com/reference/addprovideraccess.md
  - https://docs.qwist.com/reference/categorizetransactions.md
  - https://docs.qwist.com/reference/createaccesstoken.md
  - https://docs.qwist.com/reference/createaccountverification.md
  - https://docs.qwist.com/reference/createcontract.md
  - https://docs.qwist.com/reference/createincomereport.md
  - https://docs.qwist.com/reference/createmanualsync.md
  - https://docs.qwist.com/reference/createnotification.md
  - https://docs.qwist.com/reference/createonetimeaccess.md
  - https://docs.qwist.com/reference/createonetimeincomereport.md
  - https://docs.qwist.com/reference/createonetimepayment.md
  - https://docs.qwist.com/reference/createonetimeriskreport.md
  - https://docs.qwist.com/reference/createongoingaccess.md
  - https://docs.qwist.com/reference/createongoingpayment.md
  - https://docs.qwist.com/reference/createongoingriskreport.md
  - https://docs.qwist.com/reference/createpayment.md
  - https://docs.qwist.com/reference/createpaymentfromaccount.md
  - https://docs.qwist.com/reference/createqwistlink.md
  - https://docs.qwist.com/reference/createriskreport.md
  - https://docs.qwist.com/reference/createsync.md
  - https://docs.qwist.com/reference/createupload.md
  - https://docs.qwist.com/reference/createuser.md
  - https://docs.qwist.com/reference/createverifyandpay.md
  - https://docs.qwist.com/reference/deleteaccount.md
  - https://docs.qwist.com/reference/deleteclientuser.md
  - https://docs.qwist.com/reference/deletecontract.md
  - https://docs.qwist.com/reference/deletenotification.md
  - https://docs.qwist.com/reference/deletepayment.md
  - https://docs.qwist.com/reference/deleteprovideraccess.md
  - https://docs.qwist.com/reference/deleteuser.md
  - https://docs.qwist.com/reference/getaccount.md
  - https://docs.qwist.com/reference/getaccountbalance.md
  - https://docs.qwist.com/reference/getaccountverificationreceipt.md
  - https://docs.qwist.com/reference/getandgenerateincomereport.md
  - https://docs.qwist.com/reference/getartifact.md
  - https://docs.qwist.com/reference/getcategories.md
  - https://docs.qwist.com/reference/getcategoriesforaccess.md
  - https://docs.qwist.com/reference/getcategoriesforaccount.md
  - https://docs.qwist.com/reference/getcategorytree.md
  - https://docs.qwist.com/reference/getcontract.md
  - https://docs.qwist.com/reference/getcredential.md
  - https://docs.qwist.com/reference/getincomereport.md
  - https://docs.qwist.com/reference/getinsurance.md
  - https://docs.qwist.com/reference/getloan.md
  - https://docs.qwist.com/reference/getnotification.md
  - https://docs.qwist.com/reference/getpaymentchallenge.md
  - https://docs.qwist.com/reference/getpaymentchallengeofaccount.md
  - https://docs.qwist.com/reference/getpaymentinitstatus.md
  - https://docs.qwist.com/reference/getpaymentinitstatusofaccount.md
  - https://docs.qwist.com/reference/getpaymentofaccount.md
  - https://docs.qwist.com/reference/getpaymentpartners.md
  - https://docs.qwist.com/reference/getpaymentpartnersforaccess.md
  - https://docs.qwist.com/reference/getpaymentpartnersforaccount.md
  - https://docs.qwist.com/reference/getpaymentreceipt.md
  - https://docs.qwist.com/reference/getprovideraccess.md
  - https://docs.qwist.com/reference/getriskreport.md
  - https://docs.qwist.com/reference/getsecurityofaccount.md
  - https://docs.qwist.com/reference/getsyncchallenge.md
  - https://docs.qwist.com/reference/getsyncstatus.md
  - https://docs.qwist.com/reference/gettimeline.md
  - https://docs.qwist.com/reference/gettimelineforaccess.md
  - https://docs.qwist.com/reference/gettimelineforaccount.md
  - https://docs.qwist.com/reference/gettransaction.md
  - https://docs.qwist.com/reference/gettransactionofaccount.md
  - https://docs.qwist.com/reference/getuploadstatus.md
  - https://docs.qwist.com/reference/getuser.md
  - https://docs.qwist.com/reference/getversion.md
  - https://docs.qwist.com/reference/initpayment.md
  - https://docs.qwist.com/reference/initpaymentofaccount.md
  - https://docs.qwist.com/reference/listaccounts.md
  - https://docs.qwist.com/reference/listaccountsofaccess.md
  - https://docs.qwist.com/reference/listbanks.md
  - https://docs.qwist.com/reference/listcatalog.md
  - https://docs.qwist.com/reference/listcatalogclientauth.md
  - https://docs.qwist.com/reference/listclientusers.md
  - https://docs.qwist.com/reference/listcontracts.md
  - https://docs.qwist.com/reference/listcontractsofaccess.md
  - https://docs.qwist.com/reference/listcontractsofaccount.md
  - https://docs.qwist.com/reference/listcredentials.md
  - https://docs.qwist.com/reference/listinsurances.md
  - https://docs.qwist.com/reference/listinsurancesofaccess.md
  - https://docs.qwist.com/reference/listloans.md
  - https://docs.qwist.com/reference/listloansofaccess.md
  - https://docs.qwist.com/reference/listnotifications.md
  - https://docs.qwist.com/reference/listpaymentchallenges.md
  - https://docs.qwist.com/reference/listpaymentchallengesofaccount.md
  - https://docs.qwist.com/reference/listpayments.md
  - https://docs.qwist.com/reference/listpaymentsofaccount.md
  - https://docs.qwist.com/reference/listprovideraccesses.md
  - https://docs.qwist.com/reference/listsecurities.md
  - https://docs.qwist.com/reference/listsecuritiesofaccount.md
  - https://docs.qwist.com/reference/listservices.md
  - https://docs.qwist.com/reference/listsyncchallenges.md
  - https://docs.qwist.com/reference/listtransactions.md
  - https://docs.qwist.com/reference/listtransactionsofaccount.md
  - https://docs.qwist.com/reference/patchcredential.md
  - https://docs.qwist.com/reference/removepinfromprovideraccess.md
  - https://docs.qwist.com/reference/replacenotifications.md
  - https://docs.qwist.com/reference/revokeoauthtoken.md
  - https://docs.qwist.com/reference/solvepaymentchallenge.md
  - https://docs.qwist.com/reference/solvepaymentchallengeofaccount.md
  - https://docs.qwist.com/reference/solvesyncchallenge.md
  - https://docs.qwist.com/reference/updatecontract.md
  - https://docs.qwist.com/reference/updatenotification.md
  - https://docs.qwist.com/reference/updateuser.md
  merge:
    pages: 105
    deduped: 1107
    conflicts_kept_first: 0