Skip to main content
A combo is a user-defined instrument with 2–10 legs. Each leg identifies an existing market symbol and whether the combo buys or sells that leg. Combo instruments can trade through normal order entry and can be used as the symbol of an RFQ. The public polymarket.v1.ComboAPI gRPC service creates and reads combo instruments. Each RPC also has a REST endpoint. REST JSON uses lower camel case; protobuf fields use snake case.

Endpoints

All calls require bearer-token authentication and an acting participant, supplied through x-participant-id or the token’s participant_id claim. Each method has a separate per-firm rate-limit bucket with one second of burst capacity. See Rate Limits. Separately, combo creation has a participant-wide service quota of 1,000 new instruments per week across all accounts and both Retail and Institutional APIs. The quota resets Monday at 00:00 UTC; returning an existing canonical combo does not consume it.

Create a Combo

POST /v1/combos accepts a list of 2–10 unique legs:
The component symbols must be open, tradable, supported instruments. The service rejects duplicate symbols and invalid combinations. A canonical set of legs always maps to the same caoc-... combo symbol; if that combo already exists, CreateCombo returns it.

Get a Combo

GET /v1/combos?symbol=caoc-... requires the exact combo symbol and returns:
An unknown symbol returns an empty combos array. This endpoint does not paginate.

See Also

RFQ API

Create and manage combo RFQs and quotes

Combos Guide

Maker workflow and quote rules

Authentication

OAuth metadata and required scopes

Rate Limits

Endpoint-level request limits