Update an application

Update an existing application.

This endpoint only accepts JWT, which must be precalculated as described in Create a JWT.

Request​

Provide a JWT signed with a valid signing key

Path parameters

Path parameters

The Client ID of the application.

Request body

Body string

A new JWT calculated for your application, signed with a valid signing key.

Upcoming changes

On 23 March 2026, the form of the scope parameter included in the JWT payload will change to a space-separated string. For more information, see the guide: Create a JWT.

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.

List of scopes that the TPP has access to. Possible scopes to list: openid, accounts, payments, fundsconfirmation.

Upcoming changes

• Before 23 March 2026: Provided as an array of strings. For example, ["openid", "accounts", "payments", "fundsconfirmation"].
• From 23 March 2026: Provided as a space-separated string. For example, "openid accounts payments".