YAyapily
Authorisations

Update Account Pre-authorisation

Used to continue the authorisation process and for any Institution that contains the INITIATE_PRE_AUTHORISATION feature and direct user to the login screen of their financial institution in order to give consent to access account data.

Features:

  • INITIATE_ACCOUNT_REQUEST
  • INITIATE_PRE_AUTHORISATION
put/account-auth-requests

Request

  • Base URL
    https://api.yapily.com
  • Auth
    HTTP basic

Headers

consentstring required

Mandatory. The consent-token containing the user's authorisation to make the request.

psu-idstring

Conditional. Represents the user's login ID for the Institution to a personal account.

See PSU identifiers to see if this header is required.

psu-corporate-idstring

Conditional. Represents the user's login ID for the Institution to a business account.

See PSU identifiers to see if this header is required.

psu-ip-addressstring

Conditional. The IP address of the PSU.

See PSU identifiers to see if this header is required.

sub-applicationstring uuid

The sub-application ID to which event type is being subscribed to

Request body

userUuidstring uuid

User for which the authorisation request was created.

applicationUserIdstring

Conditional. User-friendly identifier of the User that provides authorisation. If a User with the specified applicationUserId exists, it will be used otherwise, a new User with the specified applicationUserId will be created and used. Either the userUuid or applicationUserId must be provided.

forwardParametersstring[]

Extra parameters the TPP may want to get forwarded in the callback request after the PSU redirect.

institutionIdstring required

Mandatory. The reference to the Institution which identifies which institution the authorisation request is sent to.

callbackstring

Optional. The server to redirect the user to after the user completes the authorisation at the Institution.

See Using a callback (Optional) for more information.

oneTimeTokenboolean

Conditional. Used to receive a oneTimeToken rather than a consentToken at the callback for additional security. This can only be used when the callback is set.

See Using a callback with an OTT (Optional) for more information.

Example request

{
  "applicationUserId": "user-234562290",
  "institutionId": "yapily-mock",
  "callback": "https://display-parameters.com",
  "accountRequest": {
    "transactionFrom": "2020-01-01T00:00:00Z",
    "transactionTo": "2021-01-01T00:00:00Z",
    "expiresAt": "2025-01-01T00:00:00Z",
    "accountIdentifiers": {
      "accountId": "500000000000000000000001",
      "accountIdentification": {
        "type": "SORT_CODE",
        "identification": "401016"
      }
    },
    "accountIdentifiersForTransaction": [
      {
        "accountId": "500000000000000000000001",
        "accountIdentification": {
          "type": "SORT_CODE",
          "identification": "401016"
        }
      }
    ],
    "accountIdentifiersForBalance": [
      {
        "accountId": "500000000000000000000001",
        "accountIdentification": {
          "type": "SORT_CODE",
          "identification": "401016"
        }
      }
    ]
  }
}

Response

Ok

linksobject
tracingIdstring

Changes

No recorded changes to this operation across all 4 revisions of this API.