> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/wallet-balance.md).

# Wallet Balance

The Wallet Balances file contains the current state of point balances for member wallets, including detailed breakdowns of earned, spent, active, and locked units.

A sample file is provided below: 

{% file src="/files/nSewbdJ0Wy14NWiZin6Q" %}

#### Available Data

* **tenantId**: Unique identifier of the tenant where the wallet is registered.
* **memberId**: Unique identifier of the member who owns the wallet.
* **walletId**: Unique identifier of the specific wallet.
* **walletTypeCode:** The code representing the type of wallet (e.g., `default`, `coins`).
* **earnedUnits**: The total lifetime number of units (points) earned by the member in this wallet.
* **transferredUnits**: The total number of units transferred related to this wallet.
* **spentUnits**: The total number of units that have been spent or redeemed by the member.
* **activeUnits**: The current balance of units available for use.
* **lockedUnits:** The number of units that are currently locked (e.g., pending activation or subject to a holding period).
* **blockedUnits**: The number of units that have been administratively blocked.
* **expiredUnits**: The total number of units that have expired without being used.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/wallet-balance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.