### Download SDK Source: https://docs.finapi.io/index Download an auto-generated SDK from https://openapitools-server-finapi-common-live.finapi.io. Adjustments may be needed for target languages. ```APIDOC ##### Download SDK The SDK you are about to download will be auto-generated by https://openapitools-server-finapi-common-live.finapi.io. Depending on the target language that you select, you might have to do some adjustments to the generated code to make it compile and function correctly. Make sure to read our FAQ about SDK generation. Also, please always read the finAPI services documentation and double-check that your code behaves as it should. If you have any trouble or questions, please contact support@finapi.io The target language for the client library ada android ape bash c clojure cpp-client cpp-qt-client cpp-restsdk cpp-tiny cpp-tizen cpp-ue4 crystal csharp dart dart-dio eiffel elixir erlang-client erlang-proper gdscript go groovy haskell-http-client java java-helidon-client java-micronaut-client javascript javascript-apollo-deprecated javascript-closure-angular javascript-flowtyped jaxrs-cxf-client jmeter julia-client k6 kotlin lua n4js nim objc caml perl php php-dt php-nextgen powershell python python-pydantic-v1 r ruby rust scala-akka scala-gatling scala-http4s scala-pekko scala-sttp scala-sttp4 scalaz swift-combine swift5 swift6 typescript typescript-angular typescript-aurelia typescript-axios typescript-fetch typescript-inversify typescript-jquery typescript-nestjs typescript-nodejs typescript-redux-query typescript-rxjs mojo-client CANCEL DOWNLOAD SDK Download OpenAPI file Download SDK ``` -------------------------------- ### Basic Authentication Source: https://docs.finapi.io/index Authenticate by specifying Username and Password. ```APIDOC ##### Basic Authentication Specify **Username** and **Password** to authenticate. **Username** **Password** CANCEL AUTHENTICATE ``` -------------------------------- ### finAPI XS2A Server Documentation Source: https://docs.finapi.io/index_product=access finAPI offers XS2A Server to banks for licensed TPPs to access payment accounts via the API Interface following the Berlin Group Standard. This documentation covers the API specification for the XS2A interface. ```APIDOC ## Welcome to finAPI XS2A Server! finAPI offers XS2A Server to the banks to allow licensed TPPs to access payment accounts via the API Interface following the Berlin Group Standard. This documentation covers the API specification for the XS2A interface. More information about the APIs and the sandbox data is available in the TPP-Developer Guide. The sandbox and production URLs are published by the banks. If you need any help with the API, contact xs2a-support@finapi.io. ``` -------------------------------- ### OAuth 2.0 Authorization Source: https://docs.finapi.io/index Authorize as a client using Client ID and Client Secret, or as a user by additionally specifying User ID and Password. ```APIDOC ##### OAuth 2.0 Authorization Specify **Client ID** and **Client secret** if you want to authorize as a client. Additionally specify **User ID** and **Password** if you want to authorize as a user. **Client ID** **Client Secret** **User ID** **Password** CANCEL AUTHORIZE AS USER AUTHORIZE AS CLIENT ``` -------------------------------- ### finAPI Access REST Services Documentation Source: https://docs.finapi.io/index_product=access Access REST Services are at the core of finAPI’s Open Banking ecosystem. The Access API enables you to receive and analyze bank account information, and execute payments. ```APIDOC ## Welcome to finAPI Access! Access REST Services lie at the core of finAPI’s Open Banking ecosystem. The Access API enables you to receive and analyze bank account information, and execute payments. The services are divided into the following sections: * The Authorization section provides the OAuth endpoints to receive and manage access tokens which you need for any other service call. * Mandator Administration and Client Configuration sections provide endpoints to configure your client. If you are a licensed TPP, the TPP Certificates and TPP Credentials sections are also relevant for your configuration. * The Users section allows you to manage your user base. * Banks, Bank Connections and Accounts provide endpoints to receive bank accounts with their Transactions/Pending Transactions or Securities. * The Categories and Labels sections provide endpoints to re-categorize and/or label transactions. * Payments and Standing Orders provide endpoints for executing money transfers, direct debits, and standing orders. * The Notification Rules section allows you to configure push notifications that will be sent to your client when certain events take place. * The Mocks and Tests section provides services which you can use to test your API integration. Note that these services can be used only on the Sandbox environment. We use cutting edge technology for constantly enhancing our services, from data analysis pipelines to an event driven system, which is built in scalable modules, that you also may use in a proprietary environment. If you are interested in this kind of usage, please feel free to contact us for an offer. Additional information about our API can be found here: Access public documentation If you need any further help with the API, contact support@finapi.io. ``` -------------------------------- ### finAPI Access API Overview Source: https://docs.finapi.io/index_product=access The finAPI Access API provides REST services for retrieving and analyzing bank account information, executing payments, and managing user data. It is divided into several key sections. ```APIDOC ## finAPI Access API Overview ### Description The finAPI Access API enables interaction with financial data and services. It is structured into the following sections: * **Authorization**: Manages OAuth endpoints for access tokens. * **Mandator Administration & Client Configuration**: For client configuration, including TPP-specific sections. * **Users**: Manages user accounts. * **Banks, Bank Connections & Accounts**: Retrieves bank accounts, transactions, and securities. * **Categories & Labels**: For re-categorizing and labeling transactions. * **Payments & Standing Orders**: Executes money transfers, direct debits, and standing orders. * **Notification Rules**: Configures push notifications for events. * **Mocks & Tests**: Services for API integration testing on the Sandbox environment. **Note**: This is a deprecated version of the API. ``` -------------------------------- ### finAPI GiroIdent Source: https://docs.finapi.io/index_product=access GiroIdent is a KYC solution based on XS2A, offering user identification through bank account access. It provides different verification levels. ```APIDOC ## finAPI GiroIdent ### Description GiroIdent is an XS2A-based KYC solution for user identification. It offers three verification types: * **GiroIdent Basis**: Verifies user's Name. * **GiroIdent Plus**: Verifies user's Name, Address, and Date of Birth (DOB), utilizing bank account access and Schufa data. * **GiroIdent GWG (§ 14 GwG)**: Verifies user's Name, Address, DOB, and Bank account details, using bank account access and Schufa data. ### Additional Information Refer to the GiroIdent public documentation for more details. ``` -------------------------------- ### finAPI Payment Source: https://docs.finapi.io/index_product=access finAPI Payment allows users to pay directly from their bank accounts. It is integrated as a sub-section of the finAPI Access API, specifically within the 'Payments' and 'Standing Orders' sections. ```APIDOC ## finAPI Payment ### Description finAPI Payment enables direct bank account payments with minimal Strong Customer Authentication (SCA). It is not a separate API but a part of the finAPI Access API. ### Related Sections Refer to the finAPI Access API sections: `Payments` and `Standing Orders`. ``` -------------------------------- ### finAPI Access API Source: https://docs.finapi.io/index Access REST Services are at the core of finAPI’s Open Banking ecosystem. The Access API enables you to receive and analyze bank account information, and execute payments. ```APIDOC ## Welcome to finAPI Access! Access REST Services lie at the core of finAPI’s Open Banking ecosystem. The Access API enables you to receive and analyze bank account information, and execute payments. The services are divided into the following sections: * The Authorization section provides the OAuth endpoints to receive and manage access tokens which you need for any other service call. * Mandator Administration and Client Configuration sections provide endpoints to configure your client. If you are a licensed TPP, the TPP Certificates and TPP Credentials sections are also relevant for your configuration. * The Users section allows you to manage your user base. * Banks, Bank Connections and Accounts provide endpoints to receive bank accounts with their Transactions/Pending Transactions or Securities. * The Categories and Labels sections provide endpoints to re-categorize and/or label transactions. * Payments and Standing Orders provide endpoints for executing money transfers, direct debits, and standing orders. * The Notification Rules section allows you to configure push notifications that will be sent to your client when certain events take place. * The Mocks and Tests section provides services which you can use to test your API integration. Note that these services can be used only on the Sandbox environment. We use cutting edge technology for constantly enhancing our services, from data analysis pipelines to an event driven system, which is built in scalable modules, that you also may use in a proprietary environment. If you are interested in this kind of usage, please feel free to contact us for an offer. Additional information about our API can be found here: Access public documentation If you need any further help with the API, contact support@finapi.io. ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.