Execution infrastructure for Polymarket.
A full execution layer on the Polymarket CLOB. Place, manage, and automate orders with institutional-grade order types and HMAC security.
Every way to execute.
The same order types the terminal runs on, exposed through a single endpoint.
Resting CLOB order at a specific price.
Immediate fill at best available depth.
Time-weighted execution to reduce market impact.
TWAP that adjusts to live market conditions.
Show a slice of size; auto-replenishes as filled.
Tracks the spread, always at inside bid or offer.
Conditional exits on price threshold.
N limit orders at stepped levels in one call.
One call to a working order.
Sign the request with your key, post the order, and the engine handles the rest: slicing, repricing, and fills stream back over WebSocket. Example shown is illustrative.
- Single-call submission for every order type
- Order updates and fills over WebSocket
- Idempotent retries and batch operations
curl -X POST https://partner-api.bravadotrade.com/v1/orders \
-H "X-API-Key: bvd_live_xxxxxxxx" \
-H "X-Signature: <HMAC-SHA256>" \
-d '{
"market": "will-btc-be-above-120k-by-eoy",
"side": "buy",
"outcome": "YES",
"type": "twap",
"size_usdc": 5000,
"duration_min": 30
}'{
"order_id": "ord_9f2e41c8",
"status": "working",
"type": "twap",
"slices_total": 30,
"slices_filled": 0,
"avg_price": null,
"created_at": "2026-06-12T14:02:11Z"
}Primitives, accounts, and provisioning.
- Split and merge: convert USDC to YES/NO outcome shares and back
- Batch cancel: cancel all or a subset of open orders in one call
- Account reads: balances, positions, open orders, activity history
- HMAC request signing, enforced per API key
- Scoped permissions: trade.read, trade.execute, trade.advanced
- Admin endpoints for key issuance, rotation, and multi-tenant setup
Build on the engine the terminal runs on.
Keys are provisioned per tenant with scoped permissions. Reach out and you can be placing orders the same day.