Skip to main content
GET
Get Rfq

Authorizations

X-River-Key-Id
string
header
required

UUID of your API key (from Settings → API Keys).

X-River-Timestamp
string
header
required

Current unix milliseconds (unix seconds also accepted). Must be within 30s of server time.

X-River-Signature
string
header
required

Base64 Ed25519 signature over the canonical request: METHOD\nPATH\nSORTED_QUERY\nTIMESTAMP\nSHA256(body) hex. See /api-reference/authentication for the full recipe.

Path Parameters

river_rfq_id
string<uuid>
required

Query Parameters

subaccount_id
string<uuid>
required

Non-custodial subaccount to query under

Response

Successful Response

An RFQ in one shape for both exchanges. Sizes are contracts (contracts_fp) or dollars (target_cost_dollars); legs are River market ids with the side each must resolve to, a single market being one YES leg. creator_user_id is only set on your own RFQs.

exchange_rfq_id
string
required

The exchange's own id for the same RFQ

status
string
required

open, closed, cancelled or expired on Polymarket US; Kalshi's own statuses

river_rfq_id
string<uuid> | null

River's id for the RFQ; absent on an RFQ that was not posted through River

exchange
string | null

kalshi or polymarket_us

river_id
integer | null

The RFQ's market; absent when it is not in the catalogue

contracts_fp
number | null
target_cost_dollars
number | null
creator_id
string | null
creator_user_id
string | null
rest_remainder
boolean | null
created_ts
string | null
updated_ts
string | null
cancellation_reason
string | null
cancelled_ts
string | null
legs
RfqLeg · object[] | null

The RFQ's legs as River markets; absent when a leg is not in the catalogue