Skip to main content
GET
Settled markets

Authorizations

X-Auth-Apikey
string
header
required

HMAC-signed API key. Send X-Auth-Apikey, X-Auth-Nonce and X-Auth-Signature.

Query Parameters

limit
integer
default:25

Markets per page. Defaults to 25, capped at 100.

Required range: 1 <= x <= 100
page
integer
default:1

Page number, from 1. Most recently settled market first.

Required range: x >= 1

Response

200 - application/json
cost
string
required

What the position cost: collateral plus the fees charged on the fills.

Example:

"36.22065000"

event_id
number | null
required
Example:

14710

event_image_url
string | null
required
Example:

null

event_slug
string | null
required

The parent event's slug — what the row links to.

Example:

"btc-updown-5m"

event_title
string | null
required
Example:

"Bitcoin Up or Down 5m"

fees
string
required

The fee part of cost.

Example:

"0.72065000"

market_id
string
required
Example:

"14738"

market_title
string | null
required
Example:

"Bitcoin Up or Down 5m — 11:15–11:20 UTC"

payout
string
required

What it paid. 0 on a market you lost.

Example:

"50.00000000"

quote_currency
string | null
required
Example:

"usdc"

result
enum<string> | null
required

How the market resolved.

Available options:
settled_yes,
settled_no
Example:

"settled_yes"

settled_at
string | null
required
Example:

"2026-09-11T11:21:37.000Z"

settlement_status
enum<string> | null
required

On-chain settlement state, or null when this holding never touched the chain (a custodial fill has nothing to confirm).

Available options:
confirmed,
pending
Example:

"confirmed"

side
enum<string>
required

The side you held. both when you bought both outcomes of the same market — rare, and reported rather than collapsed to the larger leg.

Available options:
yes,
no,
both
Example:

"yes"

volume
string
required

Contracts held at resolution.

Example:

"50"