Polymarket — List combo positions

List combo positions with the Polymarket API. Supply a user and optionally set a pagination cursor and a sort order. Use it for on-chain or crypto market research. The GET request schema also lists limit. Use the data in market research, dashboard views, or scheduled data collection for the relevant markets.

Selected price
$0 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
The wallet to anchor on. Required; combo positions are user-anchored. This execution profile requires an explicit non-null value. The original optional/nullable OpenAPI declarations remain in officialOperation.
Optional parameters (8)
First-page size. Ignored when `cursor` is supplied (the cursor's size wins).
Opaque pagination cursor from a prior response's `next_cursor`.
Combo condition id(s), comma-separated (at most 20 distinct values). `condition_id` / `conditionId` are accepted aliases.
One of `OPEN`, `REDEEMABLE`, `PARTIAL`, `RESOLVED_WIN`, `RESOLVED_LOSS`, `RESOLVED_PARTIAL`; default (absent) is the held-visibility listing. Aligned with `/v2/positions`: `OPEN` is the superset; it includes still-held redeemable positions; and `REDEEMABLE` narrows to exactly the rows whose `redeemable` flag is `true`. `REDEEMABLE` must be the sole value; the other values may be combined comma-separated and keep per-value equality semantics.
`FIRST_ENTRY` (default, except under `status=REDEEMABLE`, which defaults to `ENTRY_COST` so the largest claims lead) | `ENTRY_COST` | `CURRENT_VALUE` (alias of `ENTRY_COST`) | `UPDATED`. `FIRST_ENTRY DESC` and `UPDATED ASC` page by keyset; every other combination pages by an offset-shaped cursor. The minted cursor binds sort + direction along with the `status`/`condition` cohort, so a page-2 request needs only `?user=` and `?cursor=`; restating a filter is allowed but must agree.
`ASC` or `DESC` (default `DESC`).
Incremental-sync watermark: INCLUSIVE lower bound on `updated_at`, epoch seconds. Without a `status` filter, either watermark serves the sync view; every live row (mirror-complete), not only the held listing; a `status` filter keeps its own row visibility. The window's upper end is always capped by a short stability ceiling (about 90 seconds behind now), so a bound in the future cannot serve rows that may still move.
Incremental-sync watermark: INCLUSIVE upper bound on `updated_at`, epoch seconds; must not precede `updated_after`. See `updated_after` for the sync-view and ceiling semantics.

Sample response

{
  "data": [],
  "pagination": {
    "has_more": false,
    "limit": 2,
    "next_cursor": null,
    "offset": 0
  }
}

Response result

Response structure

Inferred from examples
  • dataunknown[]
  • paginationobject
    • has_moreboolean
    • limitinteger
    • next_cursornull
    • offsetinteger

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Polymarket — List combo positions with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.