Skip to main content
GET
Try Cobo WaaS Skill in your AI coding assistant (Claude Code, Cursor, etc.). Describe your needs in natural language to auto-generate production-ready SDK code and debug faster 🚀

Authorizations

BIZ-API-KEY
string
header
required

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

challenge_id
string<uuid>
required

The Satoshi Test challenge ID returned by the prepare or submit operation.

Example:

"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.

challenge_id
string<uuid>
required

The unique identifier of the Satoshi Test challenge.

Example:

"a1b2c3d4-e5f6-7890-abcd-ef1234567890"

from_address
string
required

The counterparty (self-custody) wallet address that must transfer the micro-deposit.

Example:

"0x1234567890abcdef1234567890abcdef12345678"

to_address
string
required

The Cobo-generated verification address that will receive the micro-deposit.

Example:

"0xabcdef1234567890abcdef1234567890abcdef12"

amount
string
required

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.

Example:

"1100001000000000"

token_id
string
required

The ID of the token used for the micro-deposit (typically the chain's native asset).

Example:

"ETH"

chain_id
string
required

The chain on which the micro-deposit is expected.

Example:

"ETH"

status
enum<string>
required

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.
Available options:
PREPARE,
PENDING,
MATCHED,
VERIFIED,
EXPIRED,
DELETED
Example:

"PENDING"

remaining_seconds
integer
required

Remaining time (in seconds) before the challenge expires. 0 when the challenge is not yet submitted or has already completed/expired.

Example:

10550

matched_txid
string | null

The on-chain transaction hash of the matching transfer, once matched.

Example:

"0xabc123..."

started_at
integer<int64> | null

Timestamp (milliseconds) when the challenge was submitted and the countdown started.

Example:

1732523887000

expires_at
integer<int64> | null

Timestamp (milliseconds) when the challenge will expire if not matched.

Example:

1732534687000