POST /api/bank/<BANKID>/authorize
INPUT
bankId – identifier of the bank the authorization flow should be initiated to (path)
userId- identifier of the user (PSU)
months - number of months to retrieve historical transactions. Transactions will be retrieved from NOW - months (MONTH) (OBSOLETE)
values -
required parameters (according to JSON provided in Step 1 GET)
provide single IBAN or multiple IBANS
{key:"iban",
value:"PL61000123450000000009040575"}
consent object - optional parameters related to PSU consent
externalId - optional external id of the consent
requestedLifespan - requested consent lifespan
daysBack - optional parameter, setting maximum days back on synchronize
sessionExternalId - external Id of the session
syncAllData - optional parameter indicating whether sync should be made for maximum available time window.
OUTPUT
success- status of the call
data - JSON file providing the list of required additional attributes (two-factor) or redirection link.
Content-Type: application/json
Example request
Example error response
Content-Type: application/json; charset=utf-8
Example success response
Content-Type: application/json; charset=utf-8
Provided URL is build by PSD2Hub based on specification for given AFI. Standard parameters provided:
client_id | Identification of the third party application id |
client_secret | Common secret between AFI and third party application |
grant_type | Should always be ‘authorization_code’ |
redirect_uri | The callback uri used during the authorization request, we do exact match! |
code | The code value received in the callback request |
code_verifier | The non-hashed value used for the code_challenge parameter in authz request |