Outstanding on-chain settlements (per fill)

GET/api/v1/me/settlementsBearer

Trading APIprice E4 · size E2 · amount E6 (integers)YES | NO

Every outstanding on-chain settlement under your name, newest first. What settlementStatus means in product terms: SETTLING ← QUEUED/SUBMITTED; RETRYING ← FAILED_RETRYABLE; FAILED ← FAILED_TERMINAL (the ledger and the chain have diverged — do not quote off it until that is resolved). Not in the list = settled. When clearing is unavailable this returns 503 rather than degrading to an empty list — an empty list would mean "everything is settled", which is a directionally wrong answer to a risk query.

Send Authorization: Bearer <token>. The token is issued by POST /api/v1/auth/verify, and expires after 24h idle or 7d after issuance.

Response

200List of outstanding settlements

The response is an array; the fields below describe each element:

jobIdstring
partition-offset-fillIndex; stable, so it can be used for idempotent deduplication
Example"job_01K5H2M3N7"
marketIdstring
Market id
Example"mkt-0001"
roleMAKER | TAKER
Your role in this fill
Example"MAKER"
settlementStatusSETTLING | RETRYING | FAILED
SETTLING = settling; RETRYING = failed and retrying; FAILED = terminally failed, awaiting manual intervention
Example"SETTLING"
takerIsYesboolean
Direction of the taker leg (true = the taker bought YES)
Examplefalse
yesPriceE4integer
Fill price in YES (1e-4); 0 when payloadCorrupted=true
Example5200
sizeE2int64
Fill size (1e-2 shares); 0 when payloadCorrupted=true
Example1000
attemptsinteger
Number of on-chain submission attempts
Example1
lastErrorstringnullable
Reason for the most recent failure (for operator triage)
chainTxDigeststringnullable
On-chain digest of the broadcast transaction
Example"9wq1XbH7c2M4p…nP4sU7wXk3Z"
payloadCorruptedboolean
true = the job payload is corrupt and the price/size detail has degraded to 0
Examplefalse
createdAtstring
When the job was created
Example"2026-09-19T00:00:00Z"
updatedAtstring
When the status last changed
Example"2026-09-19T00:00:00Z"

Switch status codes in the response example to view errors. For all codes, see the Errors page.

Request

curl -X GET "$BASE_URL/api/v1/me/settlements" \
  -H "Authorization: Bearer $TOKEN"

Response

List of outstanding settlements

[
  {
    "jobId": "job_01K5H2M3N7",
    "marketId": "mkt-0001",
    "role": "MAKER",
    "settlementStatus": "SETTLING",
    "takerIsYes": false,
    "yesPriceE4": 5200,
    "sizeE2": 1000,
    "attempts": 1,
    "lastError": null,
    "chainTxDigest": "9wq1XbH7c2M4pQ8rT1vY5zA3dF6gJ9kL2nP4sU7wXk3Z",
    "payloadCorrupted": false,
    "createdAt": "2026-09-19T00:00:00Z",
    "updatedAt": "2026-09-19T00:00:00Z"
  }
]

Response

200List of outstanding settlements

The response is an array; the fields below describe each element:

jobIdstring
partition-offset-fillIndex; stable, so it can be used for idempotent deduplication
Example"job_01K5H2M3N7"
marketIdstring
Market id
Example"mkt-0001"
roleMAKER | TAKER
Your role in this fill
Example"MAKER"
settlementStatusSETTLING | RETRYING | FAILED
SETTLING = settling; RETRYING = failed and retrying; FAILED = terminally failed, awaiting manual intervention
Example"SETTLING"
takerIsYesboolean
Direction of the taker leg (true = the taker bought YES)
Examplefalse
yesPriceE4integer
Fill price in YES (1e-4); 0 when payloadCorrupted=true
Example5200
sizeE2int64
Fill size (1e-2 shares); 0 when payloadCorrupted=true
Example1000
attemptsinteger
Number of on-chain submission attempts
Example1
lastErrorstringnullable
Reason for the most recent failure (for operator triage)
chainTxDigeststringnullable
On-chain digest of the broadcast transaction
Example"9wq1XbH7c2M4p…nP4sU7wXk3Z"
payloadCorruptedboolean
true = the job payload is corrupt and the price/size detail has degraded to 0
Examplefalse
createdAtstring
When the job was created
Example"2026-09-19T00:00:00Z"
updatedAtstring
When the status last changed
Example"2026-09-19T00:00:00Z"

Switch status codes in the response example to view errors. For all codes, see the Errors page.