Addition of a new endpoint /v2/open-banking/authorisation-gateway-url to allow clients to use an updated
Bud Connect flow, allowing their customer's to go through a new Account Connection journey. The v2 journey is
highly configurable via the use of different flags within the request payload.
Altered the List Consents endpoint to now take in an optional X-Customer-Secret field within the request headers. If done so, each consent object will now return a list of account_ids associated with the consent object in addition to a date denoting the date a which a refresh was successfully completed for that given consent object.
Deprecated Warnings endpoint within the Signal API
Added a new Money Management endpoint within the Signal API that allows clients to provide more detailed information regarding a customer's financial situation.
Added a new Customer Characteristics endpoint within the Signal API that allows clients to profile based on a customer's transactions.
Added a new Financial Insight endpoint within the Signal API that allows clients to understand a customer's overall financial situation and affordability.
The customer_secret attribute is now a required attribute on the POST Ingest Accounts endpoint.
Updated the List Transaction Response schema to detail those fields that are required and/or nullable.
Created a new Create Transaction Rule(s) endpoint that allows client to set a value of the client_label attribute against a set of customer transactions which adhere to the rules specified in the request payload.
Updated API Overview table in the introduction to include latest product set.
Addition of some optional fields to the POST Retrieve Authorisation Gateway URL endpoint. The additional fields allow clients to specify: (i) a single provider, effectively skipping the select provider screen in the customer UI; (ii) a list of providers, allowing clients to configure the list of providers shown to the customer on the select provider screen; and (iii) filter the provider list shown to the customer by the type of provider (e.g. business or personal). In addition, a connect_more_accounts_button flag can be configured to show the customer a button at the end of the connection flow that will allow them to connect to another provider without having to return to the client application.
Updated the examples within Bud's KYC endpoints to make them more usable against Bud's sandbox environment.
Addition of a new GET /v1/open-banking/account-access-consents endpoint to allow clients to query the active consents against a given customer (in relation to Bud's OB Aggregation service).