> For the complete documentation index, see [llms.txt](https://developers.bloomcredit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.bloomcredit.io/changelog/release-notes-january-7-2025.md).

# Release Notes | January 7, 2025

New releases, features, improvements, fixes, and more!

## 🚀 New Releases/Features

* Added lazy loading for tokens.
* Added a new error status of 44 for insufficient information.
* Added specific error handling for Experian.

## 🐛 Improvements and Fixes

* **UI Improvements:** We've made significant enhancements to the Bloom+ interface to improve overall usability, streamline workflows, and refresh the design. Expect a more seamless experience, a polished look, and updated branding to reflect our commitment to quality and ease of use.
* Enhanced logic on validations and account events.
* Enhanced batch account and statement API endpoints, enabling quicker bulk account and statement creation.
* Better handling of mapping between bureau error code and bloom errors.
* Security improvements for Auth V2.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.bloomcredit.io/changelog/release-notes-january-7-2025.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.