> For the complete documentation index, see [llms.txt](https://docs.xyb.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyb.co/xyb-ledger/api-reference-guides/ledger-setup-and-configuration-apis/account-management-apis.md).

# Account Management APIs

### Create an Account in a Chart

A finance team creates a new account under a specific chart to track transactions for a business unit. This ensures proper financial categorization and reporting within the platform.

{% openapi src="/files/5af2rdQ5h4ZxHvDZfiyJ" path="/api/v1/chart/{name}" method="put" %}
[openapi-ledger.json](https://content.gitbook.com/content/akJn6TxWIBAbZwLlYoVP/blobs/S917VQZQHm6OZGrj1mf5/openapi-ledger.json)
{% endopenapi %}

### List Accounts in a Chart

An admin retrieves all accounts under a specific chart to review financial structures and ensure correct account mappings. This helps with auditing and maintaining financial accuracy.

{% openapi src="/files/5af2rdQ5h4ZxHvDZfiyJ" path="/api/v1/chart/\*/" method="get" %}
[openapi-ledger.json](https://content.gitbook.com/content/akJn6TxWIBAbZwLlYoVP/blobs/S917VQZQHm6OZGrj1mf5/openapi-ledger.json)
{% endopenapi %}

#### **Best Practices for Adding Accounts**

* **Use Consistent Naming:** Clearly define account references (e.g., `MAIN_ACCOUNT`, `REVENUE_ACCOUNT`) to improve readability and maintenance.
* **Plan Wallets Ahead:** Determine the currencies or assets an account will manage before assigning wallets to avoid misconfiguration.
* **Validate Accounts:** Test transactions and verify balances to ensure expected behavior before activating the account for live usage.


---

# 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://docs.xyb.co/xyb-ledger/api-reference-guides/ledger-setup-and-configuration-apis/account-management-apis.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.