> 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/authorized-users.md).

# Authorized Users

## Authorized User

#### What is an Authorized User?

An authorized user is a person added to a credit card account by the primary cardholder; the primary consumer has contractual responsibility.

While a primary consumer can add as many authorized users as needed, only one secondary consumer with the *same* address as the primary consumer will be reported on the Metro2 J1 segment and only one secondary consumer with a *different* address than the primary consumer will be reported on Metro2 J2 segment.

It's important to note that anytime an account is updated, the secondary consumers included on the most recent update will overwrite the previously listed secondary consumers on the Metro2 J1/J2 segments.

#### Requirements

* Oauthorization (every 24 hours)
* Organization\_id (partner id)
* Create a new account → credit\_product\_id is required to assign a secondary consumer to a Credit Card
  * Consumer\_ID
  * Address\_ID
  * Designation (ECOA code)


---

# 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/authorized-users.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.