Lighthouse indexes the Canton Network and exposes what it has indexed as a read-only API. This page is the map: what each group of endpoints covers, so you can find the right area before you go into the full reference.

The complete list, with every parameter and response shape, is in the interactive reference. This page is the shorter version you read first.

A party is an identity on the network. This is the largest group, and it is where most integrations start.

You can list parties, and for a single party you can read its balance, its transactions, its transfers, its rewards and its burns. There are also profit and loss records, an export of them, marker records, development fund coupons, activity markers for the newer token standard, and the parties hosted by a validator.

Alongside those sit per-party statistics: reward totals, burn totals over a period, super validator rewards, and transaction counts per round.

Transaction and transfer history is read through the party endpoints above, with filtering so you can narrow to what you actually need rather than pulling everything and sorting it yourself.

Contracts have their own endpoints: a list, and a lookup of a single contract by its identifier.

The network moves in rounds. You can list them, fetch one by its number, and read the statistics for one round, including how markers and burns were distributed and which wallets were most active in it.

Network-wide rather than per-party: reward values per round, reward values aggregated by day, top reward values by party, top burn values by party, application coupon counts per round, marker counts and weights per round, and combined statistics per round.

This is the group most analytics and dashboard work ends up using.

Global totals, a beneficiary leaderboard, the timeline of grants through their lifecycle, a single grant by its contract identifier, and unclaimed fund events.

Vote requests, aggregated governance statistics, and the detail of a single vote request.

A paginated list of name records, and a lookup of a single record by domain name. Useful when you want to show a readable name rather than a raw identifier.

The latest Canton Coin price in dollars, and historical hourly prices over a range.

The list of featured applications, the review dashboard payload for featured application locking, mediator events, pre-approval records, and a real time view of requests per second over the last ten minutes.

A separate group covers your own account rather than network data: your current plan, the plans available, and your API keys. Key metadata can be listed, new keys created and existing keys revoked from here as well as from the interface.

These are the only endpoints that change anything, and everything they change belongs to your own account. Nothing in the API touches a wallet or moves an asset.

Movements under the newer token standard have their own endpoints, covering canonical movements with filtering and paging, and the detail of a single movement. They report movements rather than balances. The plans article has more on what is covered there.

Two endpoints report whether the service is alive and whether it is ready to serve traffic. They are there for your monitoring, not for your data pipeline.

Some groups, including the super validator and founding affiliate areas, are available on paid plans only. If an endpoint returns an authorisation error while your key is valid, check whether your plan covers that area before assuming the key is at fault.

Tell us what you are trying to build rather than which endpoint you were hoping for. There is often an existing route to the same answer, and where there is not, that is exactly the feedback that decides what gets built next.