Skip to main content
POST
/
par
Error
A valid request URL is required to generate request examples
{
  "request_uri": "<string>",
  "expires_in": 123
}

Body

​
client_assertion_type
enum<string>
required

Client Assertion using JWT Authentication, as described by RFC 7523

Available options:
urn%3Aietf%3Aparams%3Aoauth%3Aclient-assertion-type%3Ajwt-bearer
​
client_assertion
string
required

private_key_jwt client assertion

​
request
object
required

Authorization Request for submitting one-or-more Rich Authorization Request (RAR) objects that encapsulate the consent agreed between the TPP and the User.

This object defines the required JSON Web Token (JWT) payload. This does not represent a correctly serialized JWT, but provides a Schema Object that correctly defines the supported RARs.

The following Consent Combinations are supported, and indicated by the consent_combination property.

  • SingleBankDataSharingConsent: A Single Bank Data Sharing Consent

  • SingleBankServiceInitiationConsent: A Single Bank Service Initiation Consent.

  • SingleInsuranceDataSharingConsent: A Single Insurance Data Sharing Consent

  • CombinedBankDataSharingConsent: Exactly two Bank Data Sharing Consents, supported under Combined Consent rules.

  • CombinedBankServiceInitiationConsent: Exactly two Bank Service Initiation Consents, supported under Combined Consent rules.

  • CombinedBankConsent: Bank Data Sharing and Bank Service Initiation Consents, with exactly two RAR objects supported that must be mutually exclusive.

  • CombinedPaymentConsent: Combination of a Single Instant Payment with a multi-payment, with exactly two RAR objects supported, to support the existing Combined Payment profile.

Response

The request has succeeded.

​
request_uri
string
required

The request URI corresponding to the authorization request posted

​
expires_in
integer
required

A JSON number that represents the lifetime of the request URI in seconds as a positive integer