The OpenAPI specification for Finicity APIs (🇺🇸), along with a suite of tests using a generated API client and the Finicity Test Drive.
The following workflows ensure the API specification stays in good shape and can be used to consume the Finicity APIs from your application:
YAML ⤓ | Swagger Editor ⬈ | Redoc ⬈
- The test project generates an API client library from the API specification like you would do in a real application (OpenAPI Generator is used for that)
- A free Open Banking account is required to obtain your Partner ID, Partner Secret and App Key:
- Before running the tests, you need a Customer ID. For that, follow Welcome Your First Customer or run the setup script. This script will call:
addTestingCustomer
generateConnectUrl
(Finicity Connect). Simply open the URL, search for "FinBank Profiles - A" and add to your test customer all accounts fromprofile_03
.refreshCustomerAccounts
- Clone this repository
- Run
cd tests && mvn clean test -DpartnerId=*** -DpartnerSecret=*** -DappKey=*** -DcustomerId=***
- Fork this repository
- Go to Settings > Secrets > Actions
- Create new repository secrets:
PARTNER_ID
,PARTNER_SECRET
,APP_KEY
andCUSTOMER_ID
- Enable workflows in the Actions tab
- Click Run workflow under API Client Tests. Expected result: ✔️
The Finicity API specification and a generated API client are the only things you need to call Finicity from your application.
- For other software development frameworks and languages, see: OpenAPI Generator > Generators List.
- You may also be interested in trying our Postman collection.
When updating the Finicity API specification:
- Ensure it can be rendered without errors in Swagger Editor or Redoc
- Ensure an API client can be generated using OpenAPI Generator
- Prettify the YAML using
npx prettier --write --single-quote --prose-wrap always finicity.yaml
- Update and/or add tests to the test project