• General bug fixes and improvements across examples, schemas, endpoints descriptions, names and sectioning titles.
  • 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.
  • Added a new Submit Authorisation Codes endpoint for use within the Payments flows when using Bud as a technical service provider.
  • 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.
  • Updated the List Transaction Response schema to detail the addition of the new carbon tracker enrichment field.
  • 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.
  • Removed deprecated Financial Assistant endpoints.
  • 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).
  • Addition of a new "Regular Payment Changed" Insight to the Warnings Endpoint (that forms part of Bud's Signal Product).
  • Bugfix: addition of the required mobile_phone_number field to the request payload of the Switch Supplier endpoint within the Energy Switching API to align to the implementation of the API itself.
  • Bugix: the format of the annual_spend.amount field within the request payload of the kWh Estimation endpoint now states that is should be a number (as opposed to a string) to align to the API itself.
  • Fixed bug in the List Accounts endpoint for Bud's OB Aggregation service - the response data object now details all the returned fields as expected.
  • Removed the deprecated List Account Balances endpoint from the documentation entirely.
  • Added a new Ingest Accounts endpoint within the Enrichment API that allows clients to provide more detailed information regarding a customer's account.