Changelog
Back to All

Release - 16/09/2020

about 3 years ago by Bradley McInnes

Release Overview

Lots of updates in this release, some of which are breaking changes. Please see below for details.

Breaking Changes

Open Wealth Scope Changes

GET /customer

  • The name field has been split into separate givenName and familyName fields.
  • emailAddress has been replaced by an array that can return multiple emails with an optional associated type.
    • emailAddress --> emails [array]
      • email
      • type

Other Updates

POST /account-access-consent

The following additional optional parameters have been added:

  • accountServicerId - If you wish to direct the authorisingUser to a particular ASP this should be populated with the relevant accountServiceId.
  • consentTypes - The data points you wish to gain consent from your end-user to access on their behalf e.g. ReadAccounts. Must be a subset of the values configured as part of the Application setup. If omitted will default to the full list of values configured against the Application.

GET /transactions

The following additional resource fields have been added:

  • createdAt - when the record was first fetched from the ASP
  • updatedAt - when the record was last fetched from the ASP
  • sourceInstrument - represents the instrument data as presented by the ASP

GET /documents Endpoint

Retrieve metadata about documents generated on an ASP. Documents are in the context of a customer that has a relationship with the authorisingUser. Please see the API reference documentation for further detail.

Single active consent record

There can now only be one active consent record for a given authorising user and ASP pairing at any one time. Requesting a new consent for an existing pairing will revoke the previous consent.

Schema definition for the ‘expand’ query parameter

The OpenAPI schema definitions for the expand parameters present on various GET endpoints has been changed to list out the valid enumerations for each endpoint.