Skip to main content
POST
Pre-flight proposed terms
See the RFQ Trades Partner API guide for the full trade flow.

Authorizations

RFQ-Key-Id
string
header
required

The public half of the partner's API key.

RFQ-Timestamp
string
header
required

Unix seconds, within 30 seconds of server time.

RFQ-Signature
string
header
required

base64url(HMAC-SHA256(secret, timestamp + method + path + body)), padded.

Body

application/json
operation
enum<string>
required

split: both sides buy, one YES and one NO. merge: both sides sell, one YES and one NO. trade: one side buys an outcome token from the other.

Available options:
split,
merge,
trade
price
string
required

The agreed price in (0, 1). The YES price for a split or merge, the traded token's price for a trade.

Example:

"0.65"

shares
string
required

A base-10 integer in 6-decimal units.

Pattern: ^[0-9]+$
Example:

"65000000"

parties
object
required

Keyed yes and no for a split or merge, buyer and seller for a trade.

marketId
string

Required unless marketSource is combo.

marketSource
enum<string>
default:gamma

gamma for a Polymarket market id, bespoke for a bespoke market, combo for a market defined by its legs.

Available options:
gamma,
bespoke,
combo
legs
object[]

The combo's legs, for marketSource combo only.

combination
enum<string>

The combo operator. Omitted means and.

Available options:
and
token
enum<string>

The outcome token that changes hands, for trade only.

Available options:
yes,
no
priceTolerance
string

Tightens the price band to this fraction of the mark, e.g. 0.05 for ±5%. Wider than the default is refused.

Response

The verdict on each check.

valid
boolean
required

Whether a submission of these terms would be accepted now.

checks
object
required
checkedAt
string<date-time>
required