Balances and UTXOs of many addresses

POST/esplora/api/wallet/addresses

Wallet API v1.0.0 · Wallet batch

Not part of Esplora. One entry per requested address, in request order (duplicates included). An entry has either the data or an error, never neither, so a missing result is never mistaken for a zero balance. The data is exactly what GET /address/{address} and GET /address/{address}/utxo return; tx_count tells used-but-empty addresses apart, for gap-limit discovery. The whole request answers from one view: send view back on the next call of the same sync, to the same host, and every batch describes the same moment. Limits: 1 to 500 addresses, at most 20 000 UTXOs in the reply, body up to 128 KB, 2 requests per second per IP (burst 30).

Example

curl -X POST 'https://api.tensorcash.org/esplora/api/wallet/addresses' \
  -H 'Content-Type: application/json' \
  --data '{"addresses":["tc1qmvalge7mnhct9qj5uua8rn0dmjcyh6fmvrr46j"]}'

Parameters

No parameters.

Request body

application/json WalletAddressesRequest

Responses

Status	Description	Body
`200`	One entry per requested address	application/json `WalletAddressesResponse`
`400`	Bad body, more than 500 addresses, or more than 20 000 UTXOs in the reply	text/plain `string`
`410`	`view expired`: restart the sync without `view`	text/plain `string`
`413`	Body over 128 KB	text/plain `string`
`503`	`Index syncing: n/m`	text/plain `string`

Schemas

`WalletAddressesRequest`

Field	Type	Required	Description
`addresses`	`string[]`	Yes	1 to 500 addresses.
`view`	`string`	—	Optional: the `view` of an earlier response from the same host, to answer from that state.

`WalletAddressesResponse`

Field	Type	Required	Description
`tip`	`Tip`	Yes
`view`	`string`	Yes	Opaque id of the state this answer comes from. Send it back to pin later calls to it.
`addresses`	`WalletAddressEntry \| AddressError[]`	Yes	One entry per requested address, in request order.

`Tip`

Field	Type	Required	Description
`height`	`integer`	Yes
`hash`	`string`	Yes

`WalletAddressEntry`

Field	Type	Required
`address`	`string`	Yes
`chain_stats`	`ChainStats`	Yes
`mempool_stats`	`ChainStats`	Yes
`utxo`	`Utxo[]`	Yes

`ChainStats`

Field	Type	Required	Description
`funded_txo_count`	`integer`	Yes	Outputs received.
`funded_txo_sum`	`integer`	Yes	Satoshis received.
`spent_txo_count`	`integer`	Yes	Outputs spent.
`spent_txo_sum`	`integer`	Yes	Satoshis spent.
`tx_count`	`integer`	Yes	Transactions touching the address.

`Utxo`

Field	Type	Required	Description
`txid`	`string`	Yes
`vout`	`integer`	Yes
`status`	`TxStatus`	Yes
`value`	`integer`	Yes	Satoshis.

`TxStatus`

Field	Type	Required	Description
`confirmed`	`boolean`	Yes	False while the transaction is in the mempool.
`block_height`	`integer`	—	Confirmed only.
`block_hash`	`string`	—	Confirmed only.
`block_time`	`integer`	—	Block timestamp, Unix seconds. Confirmed only.

`AddressError`

Field	Type	Required	Description
`address`	`string`	Yes
`error`	`string`	Yes	`Invalid address`, or `Too many unspent transaction outputs (>5000)`.

Source: tensorcash-wallet-api (tensorcash-api) v1.0.0 (772799e) · bobponey · MIT
OpenAPI spec (JSON): /docs/api/wallet-api.openapi.json