docs: sync with docs.polymarket.com - 2026-05-08
This commit is contained in:
@@ -21,7 +21,9 @@ Your **builder code** is a `bytes32` identifier tied to your builder profile. Fi
|
||||
That's the only credential you need for attribution — no HMAC signing, no separate API key, no special headers.
|
||||
|
||||
<Note>
|
||||
Builder codes are public identifiers — they appear onchain in the `builder` field of every order you attribute. Only you control which orders include your code, so keep it scoped to apps you own.
|
||||
Builder codes are public identifiers — they appear onchain in the `builder`
|
||||
field of every order you attribute. Only you control which orders include your
|
||||
code, so keep it scoped to apps you own.
|
||||
</Note>
|
||||
|
||||
***
|
||||
@@ -39,8 +41,8 @@ Pass `builderCode` in the order struct on every order you submit. The SDK serial
|
||||
chain: 137,
|
||||
signer,
|
||||
creds: apiCreds,
|
||||
signatureType: 2,
|
||||
funderAddress,
|
||||
signatureType: 3,
|
||||
funderAddress: depositWalletAddress,
|
||||
});
|
||||
|
||||
const response = await client.createAndPostOrder(
|
||||
@@ -66,8 +68,8 @@ Pass `builderCode` in the order struct on every order you submit. The SDK serial
|
||||
chain_id=137,
|
||||
key=private_key,
|
||||
creds=api_creds,
|
||||
signature_type=2,
|
||||
funder=funder_address,
|
||||
signature_type=3,
|
||||
funder=deposit_wallet_address,
|
||||
)
|
||||
|
||||
response = client.create_and_post_order(
|
||||
@@ -119,13 +121,17 @@ Each `BuilderTrade` includes: `id`, `market`, `assetId`, `side`, `size`, `price`
|
||||
|
||||
<AccordionGroup>
|
||||
<Accordion title="Volume not appearing on the leaderboard">
|
||||
* Confirm your `builderCode` is correctly attached to every order
|
||||
* Check that orders are being matched (not just placed)
|
||||
* Allow up to 24 hours for volume to appear on the leaderboard
|
||||
<ul>
|
||||
<li>Confirm your `builderCode` is correctly attached to every order</li>
|
||||
<li>Check that orders are being matched, not just placed</li>
|
||||
<li>Allow up to 24 hours for volume to appear on the leaderboard</li>
|
||||
</ul>
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Invalid builder code">
|
||||
Verify the code matches what's shown on [your Builder Profile](https://polymarket.com/settings?tab=builder). Builder codes are `bytes32` hex values starting with `0x`.
|
||||
Verify the code matches what's shown on [your Builder
|
||||
Profile](https://polymarket.com/settings?tab=builder). Builder codes are
|
||||
`bytes32` hex values starting with `0x`.
|
||||
</Accordion>
|
||||
</AccordionGroup>
|
||||
|
||||
|
||||
@@ -10,9 +10,10 @@ All orders on Polymarket are expressed as **limit orders**. Market orders are su
|
||||
|
||||
<Info>
|
||||
The SDK handles EIP-712 signing and submission for you. If you prefer the REST
|
||||
API directly, see [Authentication](/api-reference/authentication) for constructing the
|
||||
required headers and the [API Reference](/api-reference/introduction) for full endpoint
|
||||
documentation including the raw order object fields and request/response schemas.
|
||||
API directly, see [Authentication](/api-reference/authentication) for
|
||||
constructing the required headers and the [API
|
||||
Reference](/api-reference/introduction) for full endpoint documentation
|
||||
including the raw order object fields and request/response schemas.
|
||||
</Info>
|
||||
|
||||
***
|
||||
@@ -501,7 +502,10 @@ Place up to **15 orders** in a single request:
|
||||
|
||||
## Order Options
|
||||
|
||||
Every order requires two market-specific options: `tickSize` and `negRisk`. For details on signature types (`0` = EOA, `1` = POLY\_PROXY, `2` = GNOSIS\_SAFE), see [Authentication](/api-reference/authentication#signature-types-and-funder).
|
||||
Every order requires two market-specific options: `tickSize` and `negRisk`. For
|
||||
details on signature types (`0` = EOA, `1` = POLY\_PROXY, `2` = GNOSIS\_SAFE,
|
||||
`3` = POLY\_1271 deposit wallet), see
|
||||
[Authentication](/api-reference/authentication#signature-types-and-funder).
|
||||
|
||||
### Tick Sizes
|
||||
|
||||
@@ -550,7 +554,8 @@ Multi-outcome events (3+ outcomes) use the Neg Risk CTF Exchange. Pass `negRisk:
|
||||
|
||||
<Tip>
|
||||
Both values are also available on the market object: `minimum_tick_size` and
|
||||
`neg_risk`. In Rust, the order builder auto-fetches both — you don't need to look them up manually.
|
||||
`neg_risk`. In Rust, the order builder auto-fetches both — you don't need to
|
||||
look them up manually.
|
||||
</Tip>
|
||||
|
||||
***
|
||||
@@ -570,8 +575,8 @@ $$
|
||||
|
||||
<Warning>
|
||||
Orders are continuously monitored for validity — balances and allowances are
|
||||
tracked in real time. Any maker caught intentionally abusing these checks
|
||||
will be blacklisted.
|
||||
tracked in real time. Any maker caught intentionally abusing these checks will
|
||||
be blacklisted.
|
||||
</Warning>
|
||||
|
||||
### Sports Markets
|
||||
|
||||
Reference in New Issue
Block a user