Create Hosted Consent Request
Used to initiate a consent request using Yapily Hosted Pages.
Documentation Index
Fetch the complete documentation index at: https://docs.yapily.com/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Use HTTP Basic Authentication with your Application ID as username and Application Secret as password. Manage credentials in the Yapily Console. See Authentication for details.
Headers
The sub-application ID to which event type is being subscribed to
Body
Specifies the institution requirements for making the payment. Skips the bank selection screen in payment flow if the institutionId and institutionCountryCode are provided.
URL of your server to redirect the user after completion of the consent flow.
"https://tpp-application.com"
Conditional. Yapily Identifier for the User returned by the create user step POST /users. You must provide either a userId or applicationUserId.
Conditional. Your own User reference. This field allows you to use your own unique references for individual users. Where the User reference doesn't have an associated Yapily userId, a new userId is created and linked to it. You must provide either a userId or applicationUserId.
Specifies the language and location preferences of the user.
Used to receive a oneTimeToken rather than a consentToken at the redirectUrl for additional security.
"false"
Conditional. Used to further specify details of the Consent to request
Conditions:
- Mandatory to specify the individual scopes to request from the user at the
Institutionfor an account authorisation - Mandatory to specify an expiry time on the created
Consentat which time will render it unusable - Mandatory to specify the date range that the created
Consentwill be able to access transactions for (given the range is support for theInstitution)