Polymarket — List combo positions
polymarket_get_v2_positions_combosCombo positions for a user, in the standard Uses the caller's OpenAny gateway credentials. Charges and authorization are determined by the gateway.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| user | Yes | 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. | |
| limit | No | First-page size. Ignored when `cursor` is supplied (the cursor's size wins). | |
| cursor | No | Opaque pagination cursor from a prior response's `next_cursor`. | |
| status | No | 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. | |
| sort_by | No | `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. | |
| condition | No | Combo condition id(s), comma-separated (at most 20 distinct values). `condition_id` / `conditionId` are accepted aliases. | |
| updated_after | No | 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. | |
| sort_direction | No | `ASC` or `DESC` (default `DESC`). | |
| updated_before | No | 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. |