> 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/furnishment/statements/statement-api-errors.md).

# Statements API Errors

Overview of API errors related to Statements

When using the Bloom API and manipulating Account Resources you can encounter errors.

The Bloom API responds with detailed error codes on top of HTTP standard error.

Here is an example error payload:

{% code title="JSON" %}

```json
{
  "errors": [
    {
      "status_code": 511,
      "title": "Associated relationship not found",
      "detail": "The provided ID is either invalid or was not found: f7ea4de7-3b80-42ff-b2d0-5d3c3852da04",
    }
  ]
}
```

{% endcode %}

{% hint style="info" %}
**All Statements related errors will start with `5`.**
{% endhint %}

<br>

### Request Errors

| Error Code | HTTP Status Code | Title                             | Description                                                                                 | Solution                                                         |
| ---------- | ---------------- | --------------------------------- | ------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| 510        | 404              | Not Found                         | The ID provided in URL was not found in the organization                                    | Make sure the ID provided in URL is correct.                     |
| 511        | 400              | Associated relationship not found | The ID provided in a field in the request body, was not found for the current organization. | Make sure the ID described in the message exits in organization. |
| 512        | 400              | Value not in enum                 | Provided value is not part of Enum.                                                         | Verify documentation for valid enum value.                       |
| 513        | 400              | Required Field is missing         | Requested payload value should not be null.                                                 | Make sure all requested fields are present in payload            |

<br>

### Business Logic Validation Error

| Error Code | HTTP Status Code | Title                     | Description                                                                                                              |
| ---------- | ---------------- | ------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| 530        | 400              | Internal Validation Error | <p>There is an inconsistency between two or more field provided in the<br>request data. e.g. Open Date > Closed Date</p> |
| 531        | 400              | Update not allowed        |                                                                                                                          |
| 532        | 400              | Delete not allowed        |                                                                                                                          |
| 533        | 400              | Event not allowed         |                                                                                                                          |
| 534        | 400              | Requires start event      |                                                                                                                          |
| 535        | 400              | Reverse not allowed       |                                                                                                                          |

<br>

### Metro2 Compliance Validation

| Error Code | HTTP Status Code | Title                           |
| ---------- | ---------------- | ------------------------------- |
| 550        | 400              | Failed Credit Report Validation |
| 551        | 400              | Invalid Special Comment Code    |
| 570        | 400              | Incompatible Metro2 State       |
| 571        | 400              | Invalid Bureau                  |
| 572        | 400              | Organization Settings not found |

<br>

### Logic Errors

| Error Code | HTTP Status Code | Title                                         |
| ---------- | ---------------- | --------------------------------------------- |
| 580        | 500              | Logic Error Occured, please contact support   |
| 581        | 409              | Associated Relationship Id already exists     |
| 582        | 409              | Internal defined unique constraints violation |
| 590        | 500              | Error during consumer detokenisation          |
| 591        | 500              | Invalid consumer data                         |
| 592        | 500              | Invalid address data                          |


---

# 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/furnishment/statements/statement-api-errors.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.