Combos
Multi-leg combo (parlay) orders and the combo eligibility catalog
The Combos API handles multi-leg combo (parlay-style) trades that bundle several market legs into a single order. Combo creation is asynchronous — POST /api/v1/combos returns 202 Accepted and settlement runs in the combos worker domain. The public combo catalog endpoints report which legs can be combined for a given game.
Endpoints
| Method | Path | Auth | Description |
|---|---|---|---|
| GET | /api/v1/combos | Bearer | List the caller's combo orders |
| POST | /api/v1/combos | Bearer | Create a combo order (async — returns 202 Accepted) |
| GET | /api/v1/combos/:id | Bearer | Get a single combo order |
| POST | /api/v1/combos/:id/exit | Bearer | Exit a combo order early via a SELL RFQ |
| POST | /api/v1/combos/:id/redeem | Bearer | Redeem a winning combo order (manual fallback) |
| GET | /api/v1/combo/markets | No | List catalog markets eligible for a game, with per-leg addable flags |
| POST | /api/v1/combo/eligible | No | Check whether a set of legs can be combined |
Notes
- Combos are a Polymarket-only feature. Kalshi (DFlow-sourced) events have no combo catalog.
- Combo placement is async: poll
GET /api/v1/combos/:id(or subscribe to theuser:combo-ordersWebSocket channel) for status transitions. exitcloses an open combo early via a SELL request-for-quote;redeemis a manual fallback for claiming a settled winning combo.