• Addition of the period field to the GET /v1/salary endpoint to provide an indication into any regulatory associated with a predicted salary transaction.

• [BREAKING] Deprecated the use of bank_name in relevant schemas within Bud’s OB Aggregation API in favour of of the field provider
• Updated Affordability API title to Financial Review API and provided an updated description of the API.
• Updated the product table within the introduction to reflect new titles and descriptions across Bud’s API services.

• Added a new endpoint for the OB Aggregation TSP flow - POST /v1/open-banking/authorisation-codes. It allows clients to send back the parameters they receive from the bank once the customer has completed the authorisation process. This allows Bud to match the state to the relevant task id, and also provides the relevant code that will allow Bud to start fetching the customer’s data from the provider.

• Addition of international updates to payments APIs
• Updated energy switching meters example to ensure that it will return meter information for the address given in the example.

• Financial Assistant service added to the Insights API. This includes three brand new endpoints that help customers to better manage their financial world.
  • Retrieve Warnings: provides a list of potential scenarios where a customer might suffer some financial expense (e.g. in their overdraft, cannot cover bills, late payment and late income)
  • Retrieve Trends: provides the key trends associated with a customer’s transactional data broken down by month
  • Retrieve Forecast - provides a list of the regular and predicted transactions over a given period, noting whether they are booked, pending or predicted.
• Affordability Service added to the documentation, including a brand new endpoint to help clients to assess their customers affordability. The Create Spending Groups endpoint allows clients to create their own custom group, e.g. Discretionary Spend, where they can select which of Bud’s categories and/or subcategories will make up the group. All transactions for that customer assigned to the categories/subcategories within the group will be bucketed up and the client will be able to see the total income and expenditure in those categories over a given period of time.

• Added Payments: List Payment Status endpoint in order to retrieve paginated details of multiple payment ids based on header filters
• General bug fixes and improvements across examples, schemas, endpoints descriptions, names and sectioning titles.

• Addition of Bud’s Payment Initiation API. The endpoints provide clients with the functionality to allow their customers to make payments from one of their bank accounts, to a chosen recipient. In their first iteration, customers are able to authorise a single payment from one of their UK based bank accounts to another UK bank account.
• Addition of a Category Totals endpoint. The endpoint allows clients to retrieve the total amount of money that is moving into and out of their customers' connected bank accounts, broken down by transaction category. The endpoint breaks the totals down by both tier 1 and tier 2 type categories (as is provided by Buds dual layered categorisation engine).
• Acceptance of a new transaction schema format for all 1st Party Enrichment Endpoints. All of Bud’s first party data enrichment endpoints (i.e. POST/v1/categorise/double-cat, POST/v1/regular-payments, POST/v1/merchants) are now able to accept the transaction format outputted by TrueLayer. This makes it even easier for those clients who are using TrueLayer as an aggregator to get the use of Bud’s enrichment services.