> 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/data-access/status-codes.md). # Credit Data Orders Order Credit Data for Consumers using Bloom's Data Access API When you submit a credit data order through Bloom's Data Access API, you will receive a response with an order state and status code. This page provides information related to these fields. ## Order States | State | Description | Codes | Terminal? | | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | --------- | | `PENDING` | Initial state for all orders, waiting to be processed. | [00](#id-00) | ❌ | | `INGESTED` | Order is currently being routed to the bureau data provider(s). | [20](#id-20) | ❌ | | `PROCESSING` | Order is in processing if it's being: 1. Retrieved from the bureau 2. Encrypted and stored on Bloom's systems 3. Parsed and converted for our API presentation layer |

21
22

| ❌ | | `SUCCESS` | The order was successfully submitted and processed by the credit data provider. Successful orders could result in Hits, where the data is made available for querying via our GraphQL API; or could result in a condition where the bureau does not return a credit report (No-hit, Frozen/Blocked, or consumer is under 18) and no data is available to be queried. |

30
31
32
33
34

| ✅ | | `FAILED` | Order has failed to process, which can include any of the reasons below: 1. Bureau was unresponsive or had API errors. 2. Bloom had internal errors when processing the order. |

40
41
42
43

| ✅ | | `REJECTED` | Order was rejected from being processed by Bloom due to some malformed client request. |

10
11
12
13

| ✅ | | `CANCELED` | Order processing was cancelled. |

50
51

| | | `DELETED_RETENTION` | Previously submitted order has been deleted due to retention rules and credit data is erased from Bloom's systems, no longer viewable from the API. |

60
61
62

| ✅ | ## Code Details ## 00 The order request was accepted, and is waiting to be processed. *** ## 10 The order is was rejected because the provided SKU is not enabled. *** ## 11 The order is was rejected because the provided consumer ID is not valid or does not exists. *** ## 12 The order is was rejected because the provided portfolio ID is not valid or does not exists. *** ## 13 The order is was rejected because the provided consumer age is under 18 years old. *** ## 20 The order request is queued for processing. *** ## 21 The bureau is being queried to retrieve the credit data. *** ## 22 The credit data is being parsed from the bureau. *** ## 30 The request was completed and the bureau returned a Hit. *** ## 31 The bureau was not able to access the requested consumer's credit report due to a Frozen or blocked file. *** ## 32 The bureau was not able to match the requested consumer with any credit report, returning a No-Hit status *** ## 33 The request was completed using a partially created consumer without a date of birth, but the bureau detected that the requested consumer age is under 18 years old. *** ## 34 The bureau returned a Fraud, Security, or Military alert that may require additional identify verification. More information is stated in the GQL/Full Report API if it was provided. *** ## 40 The request failed due to a Bureau validation error *** ## 41 The request failed due to a Bureau availability error. The max number of retries was reached. *** ## 42 The request failed due to a Bureau system error. *** ## 43 The request failed due to a Bloom system error. *** ## 50 The request was canceled by client. *** ## 51 The request was canceled by Bloom. *** ## 60 Data retention threshold reached. *** ## 61 Data deleted at consumer’s request. *** ## 62 Data deleted at client’s request. *** ## 99 The request sent is malformed, or some of the informed fields didn't pass our service validations. Make sure the values sent are matching the correct type defined in the specification. More details will be provided directly in the response you get. --- # 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/data-access/status-codes.md?ask=&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.