> 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/consumer-events-copy.md).
# \[Draft - 9338] Consumer Events
## Bankruptcy
In order to report these events in Metro2, need to provide details about each event in the respective endpoints.
For them to be captured in the reporting cycle of a furnishment, the event's effective date needs to occur ***before*** or ***on*** the statement date.
### Different Bankruptcy Events:
All bankruptcy start with a `Filed` event and evolve following the black arrows described above. Bankruptcy events can be reversed to a previous existing event following the blue arrows. If there are no previous event, the bankruptcy will no longer be reported.
| Bankruptcy Events | Description |
| -------------------- | --------------------------------------------------------------------------------------------------------------------- |
| `Filed` | Starts the bankruptcy process |
| `Reaffirmed` | An agreement that accounts in question will be paid in full or partially. |
| `Reaffirm Rescinded` | Bankruptcy has been rescinded by court ruling. |
| `Discharged` |
Bankruptcy has been discharged and debts have been forgiven. Successfully completes the bankruptcy process.
|
| `Withdrawn` | Bankruptcy voluntarily dismissed by consumer. |
{% hint style="info" icon="lightbulb" %}
**Good to know**
* When you report a bankruptcy, it will be reported on all accounts related to that consumer.
* When you discharge a bankruptcy, you can choose which accounts the bankruptcy should be *excluded* from.
{% endhint %}
---
# 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/consumer-events-copy.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.
