Open Banking API
Get an application
api
get
/register/{ClientId}

Get an application

Retrieve an already registered application.

Authorization​

Each Open Banking API must contain an authorization header in the following format to make a call: Bearer <yourAccessToken>.

Before you start, ensure that you've got an access token with the correct scope using the /token endpoint. You need to get the authorization code first and exchange it for an access token.

danger

Never share your access_token with anyone, as it can be used to access the banking data that you have access to and initiate transactions.

For more information, see Tutorial: Get account and transaction information and Tutorial: Initiate your first payment as examples.

x-jws-signature​

Open Banking API Payment requests additionally require a JSON Web Signature (JWS) which needs to be added to the header of the request. The JWS signature must be obtained using the full content of the payload.

Request​

Path Parameters
Path Parameters

The Client ID of the application.

Response​

Application data

Response body
Body object

The Client ID used to identify the application.

Possible values: [tls_client_auth]

Specifies the authentication method for the /token endpoint.

Currently, only tls_client_auth is supported.

Distinguished name (DN) of the transport certificate used by the TPP.

Possible values: [tls_client_auth]

The signing algorithm used to sign the id_token JWTs. Currently, only PS256 is supported.

Possible values: [tls_client_auth]

The signing algorithm used to sign request objects. Currently, only PS256 is supported.

List of the registered URIs that the TPP will use to interact with the ASPSP.

Public URI endpoint where the TPP has uploaded their JWKS in JSON format.

Legal Entity Identifier or other known organisation name.

Possible values: [openid, accounts, payments, fundsconfirmations]

List of scopes granted to the TPP.

Was this page helpful?
Loading...