curl --request GET \
--url https://api.example.com/api/v1/wallet/rounds[
{
"funding_txid": "<string>",
"id": 1,
"participation": {
"inputs": [
"<string>"
],
"outputs": [
{
"amount_sat": 1,
"policy_type": "<string>",
"user_pubkey": "<string>"
}
]
},
"status": {
"error": "<string>",
"status": "sync-error"
},
"unlock_hash": "<string>",
"funding_tx_hex": "<string>"
}
]Returns all active round participations and their current status. A round participation is created when you call one of the refresh endpoints and persists until the round’s funding transaction is confirmed on-chain (2 confirmations on mainnet, 1 on testnet). The list can contain multiple entries—for example, a previous round awaiting on-chain confirmation alongside a newly submitted round waiting for the next server round to start. Confirmed and failed rounds are removed automatically by the background daemon.
curl --request GET \
--url https://api.example.com/api/v1/wallet/rounds[
{
"funding_txid": "<string>",
"id": 1,
"participation": {
"inputs": [
"<string>"
],
"outputs": [
{
"amount_sat": 1,
"policy_type": "<string>",
"user_pubkey": "<string>"
}
]
},
"status": {
"error": "<string>",
"status": "sync-error"
},
"unlock_hash": "<string>",
"funding_tx_hex": "<string>"
}
]Returns the wallet pending rounds
The round transaction id, if already assigned
Unique identifier for the round
x >= 0the round participation details
Show child attributes
the current status of the round
Show child attributes
Was this page helpful?