Get Satoshi Test challenge
This operation returns the current state of a Satoshi Test challenge — useful for polling after submission. The response contains the challenge status and remaining_seconds.
Recommended polling interval: 10–30 seconds. The challenge will transition through PENDING → MATCHED → VERIFIED once the counterparty’s transfer is observed and confirmed on chain. If the challenge is not matched within 180 minutes, the status becomes EXPIRED.
Documentation Index
Fetch the complete documentation index at: https://cobo.com/developers/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
The API key. For more details, refer to API key.
In the API playground, enter your API secret, and your API key will be accordingly calculated.
Query Parameters
The Satoshi Test challenge ID returned by the prepare or submit operation.
"a1b2c3d4-e5f6-7890-abcd-ef1234567890"
Response
The Satoshi Test challenge information (after submit or for status polling).
Full information about a Satoshi Test challenge, returned by the create and get operations.
The unique identifier of the Satoshi Test challenge.
"a1b2c3d4-e5f6-7890-abcd-ef1234567890"
The counterparty (self-custody) wallet address that must transfer the micro-deposit.
"0x1234567890abcdef1234567890abcdef12345678"
The Cobo-generated verification address that will receive the micro-deposit.
"0xabcdef1234567890abcdef1234567890abcdef12"
The exact amount (in the token's smallest unit) that must be transferred. The amount is unique per challenge and is used together with to_address to identify a matching on-chain transfer.
"1100001000000000"
The ID of the token used for the micro-deposit (typically the chain's native asset).
"ETH"
The chain on which the micro-deposit is expected.
"ETH"
The lifecycle status of a Satoshi Test challenge.
PREPARE: Challenge created (address and amount returned); the 180-minute countdown is not started yet.PENDING: Challenge submitted; countdown active, waiting for the counterparty's on-chain transfer.MATCHED: An on-chain transfer matching the expected amount has been observed; waiting for block confirmations.VERIFIED: The matched transfer reached confirmation — the address is verified.EXPIRED: Challenge was not matched within 180 minutes.DELETED: Challenge was cancelled by the client.
PREPARE, PENDING, MATCHED, VERIFIED, EXPIRED, DELETED "PENDING"
Remaining time (in seconds) before the challenge expires. 0 when the challenge is not yet submitted or has already completed/expired.
10550
The on-chain transaction hash of the matching transfer, once matched.
"0xabc123..."
Timestamp (milliseconds) when the challenge was submitted and the countdown started.
1732523887000
Timestamp (milliseconds) when the challenge will expire if not matched.
1732534687000
