OpenFinance
Development Portal

openFinance API Framework Implementation Guidelines Administrative Services (1.1)

The Berlin Group - A European Standards Initiative | info@: info@berlin-group.org | URL: https://www.berlin-group.org/

License: Creative Commons Attribution 4.0 International Public License

After conclusion of necessary contracts an API Client has to execute a technical onboarding at the openFinance API of an ASPSP. As part of the technical onboarding the ASPSP can check if all necessary contractual steps have been finished before. If everything is ok the ASPSP will assign a unique apiContractId to the API Client and will return this to the API Client as response of the technical onboarding. The API Client has to use this apiContractId for all further accesses to the extended services at the openFinance API of the ASPSP.

Submit new certificate

POST /v2/onboardings/{onboardingId}/certificates

With this POST command the API Client informs the ASPSP that he will use for future calls a new certificate (QSealC) for message signing.

Parameter Type Description
onboardingId string , required

Onboarding ID as returned with the response message to the initiation of the onboarding process.

Example: 3d9a81b3-a47d-4130-8765-a9c0ff861100

Format: uuid

Header Type Description
Digest string , optional

Integrity hash of the request body in the form SHA-256=<base64>. For an empty body, use the hash of an empty string. See Signing requests for how the Digest and signature are built.

Example: SHA-256=hl1/Eps8BEQW58FJhDApwJXjGY4nr1ArGDHIT25vq6A=

x-jws-signature string , optional

Detached JSON Web Signature over the signed request headers and body. See Signing requests for how it is constructed.

X-Request-ID string , required

Unique ID of the request, set by the initiating party and echoed back in the response.

Example: 99391c7e-ad88-49ec-a2ad-99ddcb1f7721

Format: uuid

Select a status code to see the structure and an example of the response.