> 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/docs/v2.1/furnishment/error-codes.md).

# Error Codes

The error status codes are defined by the following regular expression:

* For Client facing errors: `([0-9]{1})([0-9]{2})`

ie:

```
"errors": [  
    {  
        "status_code": 211,  
        "title": "Associated relationship not found",  
        "detail": "The provided ID is either invalid or was not found: 123456789abcdefg"  
    }  
]  
```

Where 2 represents this error occurred during an Account Event process, and the semantics of the error is "Associated relationship not found" (error code 11).

## Error Group

Defines a set of error codes grouped by a given endpoint, that may appear in other endpoints as well:

|                 | Status Code |
| --------------- | :---------: |
| Account         |    `1xx`    |
| Account Events  |    `2xx`    |
| Consumers       |    `3xx`    |
| Consumer Events |    `4xx`    |
| Statements      |    `5xx`    |

## Error numbers

The “error number” groups the semantics of the error by code:

* Request-related errors (`x10-x29`)
* Business Logic validation errors (`x30 - x49`)
* Metro2 compliance validation (`x50 - 79`)
* Logic errors (`x80-x99`)

|             Error Title             | Error Codes |                                                  Possible Reason                                                 |                                      What to Check                                      |
| :---------------------------------: | :---------: | :--------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------: |
| "Associated relationship not found" |      11     |            The ID provided in a field in the request body, was not found for the current organization.           |       Make sure the ID described in the error message exits in your organization.       |
|         "Value not in enum"         |      12     |                                      Provided value is not part of the enum                                      |               Check the doc for the available enums for the specific field              |
|     "Required field is missing"     |      13     |                                 The value in the request body should not be null                                 | Check the field mentioned in the detail section of the error and provide a valid value. |
|     "Internal validation error"     |      30     | There is an inconsistency between two or more fields provided in the request data e.g., `open date > close date` |                                                                                         |
|         "Update not allowed"        |      31     |                                                                                                                  |                                                                                         |
|         "Delete not allowed"        |      32     |                                                                                                                  |                                                                                         |
|         "Event not allowed"         |      33     |                                                                                                                  |                                                                                         |
|        "Requires start event"       |      34     |                                                                                                                  |                                                                                         |
|        "Reverse not allowed"        |      35     |                                                                                                                  |                                                                                         |
|    "Consumer action not allowed"    |      37     |                                                                                                                  |                                                                                         |
|  "Failed Credit Report validation"  |      50     |                                                                                                                  |                                                                                         |
|    "Invalid Special Comment Code"   |      51     |                                                                                                                  |                                                                                         |
|       "Transition not allowed"      |      52     |                                                                                                                  |                                                                                         |
|                                     |             |                                                                                                                  |                                                                                         |


---

# 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/docs/v2.1/furnishment/error-codes.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.