# Ledger Data Formats

Each [ledger version](/docs/concepts/ledgers) in the XRP Ledger is made up of three parts:

- **[Ledger Header](/docs/references/protocol/ledger-data/ledger-header)**: Data about this ledger version itself.
- **[Transaction Set](/docs/references/protocol/transactions)**: The transactions that were executed to create this ledger version.
- **[State Data](/docs/references/protocol/ledger-data/ledger-entry-types)**: A list of ledger entries, representing all accounts, settings, and balances as of this ledger version. (This is also called the "account state".)


## State Data

Each [ledger version](/docs/concepts/ledgers)'s state data is a set of **ledger objects**, sometimes called *ledger entries*, which collectively represent all settings, balances, and relationships at a given point in time. To store or retrieve an object in the state data, the protocol uses that object's unique **[Ledger Object ID](/docs/references/protocol/ledger-data/common-fields)**.

In the [peer protocol](/docs/concepts/networks-and-servers/peer-protocol), ledger objects have a [canonical binary format](/docs/references/protocol/binary-format). In `rippled` APIs, ledger objects are represented as JSON objects.

A ledger object's data fields depend on the type of object; the XRP Ledger supports the following types: