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...
| Seller | Pricing | Requests · 30d | Performance | Access |
|---|---|---|---|---|
PolymarketCurrent Polymarket — List combo positions · GET | $0 / call | — | —successP50— |
Run sends a real API request. Charges follow the published API contract.
Response structure
dataunknown[]paginationobjecthas_morebooleanlimitintegernext_cursornulloffsetinteger
// Inferred from response examples. Fields are optional and other fields may be returned.
export type ApiResponse = {
data?: Array<unknown>;
pagination?: {
has_more?: boolean;
limit?: number;
next_cursor?: null;
offset?: number;
};
};- Method
- GET
- Endpoint
https://api.openany.si/v1/agent-apis/polymarket/v2/positions/combos- Content type
- application/json
- Authentication
Authorization: Bearer $OPENANY_API_KEY
curl \
'https://api.openany.si/v1/agent-apis/polymarket/v2/positions/combos?limit=2&user=0x17eC161f126e82A8ba337f4022d574DBEaFef575' \
-X GET \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json'Input parameters
Fields in this listing; additional options and input encoding can vary by provider.
| Parameter | Location | Type | Required | Description |
|---|---|---|---|---|
user | URL query parametersquery | string | 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 | URL query parametersquery | integer | null | No | First-page size. Ignored when `cursor` is supplied (the cursor's size wins). minimum: 0 · maximum: 1000 |
cursor | URL query parametersquery | string | null | No | Opaque pagination cursor from a prior response's `next_cursor`. |
condition | URL query parametersquery | string | null | No | Combo condition id(s), comma-separated (at most 20 distinct values). `condition_id` / `conditionId` are accepted aliases. |
status | URL query parametersquery | string | null | 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 | URL query parametersquery | string | null | 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. |
sort_direction | URL query parametersquery | string | null | No | `ASC` or `DESC` (default `DESC`). |
updated_after | URL query parametersquery | integer | null | 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. |
updated_before | URL query parametersquery | integer | null | 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. |
Required markers inside a nested object or variant apply when that object or variant is used.
Sample response
Sample response · Documented HTTP 200 Published documentation example. Verify the actual response after an approved call.
{
"data": [],
"pagination": {
"has_more": false,
"limit": 2,
"next_cursor": null,
"offset": 0
}
}Agent integration
Copy the resource contract without sharing an API key.
View API Markdown
# 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.
## Available implementations
Polymarket · Polymarket — List combo positions: https://openany.si/markets/apis/capabilities/polymarket-list-combo-positions?offering=0362c164-c680-4af0-b273-8df543bae5e3 · $0 / call
## Selected API contract
Documentation: https://openany.si/markets/apis/capabilities/polymarket-list-combo-positions
Method: GET
Endpoint: https://api.openany.si/v1/agent-apis/polymarket/v2/positions/combos
Price: $0 / call
Provider: Polymarket
Contract revision: 3
Price source: OpenAny public API contract and documented provider unit rates. Price update time: not supplied.
Use OPENANY_API_KEY from the environment. API Key calls use your shared balance.
## Prepared request
```bash
curl \
'https://api.openany.si/v1/agent-apis/polymarket/v2/positions/combos?limit=2&user=0x17eC161f126e82A8ba337f4022d574DBEaFef575' \
-X GET \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json'
```
## API contract
```json
{
"resource_type": "api",
"name": "Polymarket — List combo positions",
"endpoint": "https://api.openany.si/v1/agent-apis/polymarket/v2/positions/combos",
"method": "GET",
"content_type": "none",
"execution_mode": "sync",
"authentication": {
"type": "bearer",
"environment_variable": "OPENANY_API_KEY"
},
"inputs": [
{
"description": "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.",
"location": "query",
"name": "user",
"nullable": false,
"required": true,
"type": "string"
},
{
"description": "First-page size. Ignored when `cursor` is supplied (the cursor's size wins).",
"location": "query",
"maximum": "1000",
"minimum": "0",
"name": "limit",
"nullable": true,
"required": false,
"type": "integer"
},
{
"description": "Opaque pagination cursor from a prior response's `next_cursor`.",
"location": "query",
"name": "cursor",
"nullable": true,
"required": false,
"type": "string"
},
{
"description": "Combo condition id(s), comma-separated (at most 20 distinct values).\n`condition_id` / `conditionId` are accepted aliases.",
"location": "query",
"name": "condition",
"nullable": true,
"required": false,
"type": "string"
},
{
"description": "One of `OPEN`, `REDEEMABLE`, `PARTIAL`, `RESOLVED_WIN`, `RESOLVED_LOSS`,\n`RESOLVED_PARTIAL`; default (absent) is the held-visibility listing.\n\nAligned with `/v2/positions`: `OPEN` is the superset; it includes\nstill-held redeemable positions; and `REDEEMABLE` narrows to exactly\nthe rows whose `redeemable` flag is `true`. `REDEEMABLE` must be the\nsole value; the other values may be combined comma-separated and keep\nper-value equality semantics.",
"location": "query",
"name": "status",
"nullable": true,
"required": false,
"type": "string"
},
{
"description": "`FIRST_ENTRY` (default, except under `status=REDEEMABLE`, which defaults\nto `ENTRY_COST` so the largest claims lead) | `ENTRY_COST` |\n`CURRENT_VALUE` (alias of `ENTRY_COST`) | `UPDATED`. `FIRST_ENTRY DESC`\nand `UPDATED ASC` page by keyset; every other combination pages by an\noffset-shaped cursor. The minted cursor binds sort + direction along\nwith the `status`/`condition` cohort, so a page-2 request needs only\n`?user=` and `?cursor=`; restating a filter is allowed but must agree.",
"location": "query",
"name": "sort_by",
"nullable": true,
"required": false,
"type": "string"
},
{
"description": "`ASC` or `DESC` (default `DESC`).",
"location": "query",
"name": "sort_direction",
"nullable": true,
"required": false,
"type": "string"
},
{
"description": "Incremental-sync watermark: INCLUSIVE lower bound on `updated_at`,\nepoch seconds. Without a `status` filter, either watermark serves the\nsync view; every live row (mirror-complete), not only the held\nlisting; a `status` filter keeps its own row visibility. The window's\nupper end is always capped by a short stability ceiling (about 90\nseconds behind now), so a bound in the future cannot serve rows that\nmay still move.",
"location": "query",
"name": "updated_after",
"nullable": true,
"required": false,
"type": "integer"
},
{
"description": "Incremental-sync watermark: INCLUSIVE upper bound on `updated_at`,\nepoch seconds; must not precede `updated_after`. See `updated_after`\nfor the sync-view and ceiling semantics.",
"location": "query",
"name": "updated_before",
"nullable": true,
"required": false,
"type": "integer"
}
],
"billing": {
"currency": "USD",
"mode": "fixed",
"priceMicroUsd": "0",
"rounding": null,
"unit": "call",
"unitQuantity": null
},
"examples": [
{
"http_status": 200,
"name": "Documentation example",
"request": {
"body": null,
"headers": {},
"path": {},
"query": {
"limit": 2,
"user": "0x17eC161f126e82A8ba337f4022d574DBEaFef575"
}
},
"response_body": {
"data": [],
"pagination": {
"has_more": false,
"limit": 2,
"next_cursor": null,
"offset": 0
}
}
}
]
}
```Error handling
| Status | Next step |
|---|---|
400 | Check the offering and request fields. |
401 / 403 | Verify your credentials and access permissions. |
402 | Inspect the selected access mode and returned payment requirements. |
429 | Respect the returned rate limit and retry guidance. |
5xx | Inspect the error and usage record before retrying a paid operation. |
Documentation example
Published documentation example. Verify the actual response after an approved call.
Prepare your environment
Use a terminal with cURL installed.
Use an OpenAny API key with shared-balance access. Confirm availability and price before running; a call may charge your balance.
Set the key in your terminal using the hidden prompt below. Keep its value out of source files and logs.
Terminal · macOS / Linuxprintf 'OpenAny API key: ' read -r -s OPENANY_API_KEY export OPENANY_API_KEY printf '\n'Run the request
Paste the complete command below into your terminal.
Values to replace before running 9
Review these request fields before running. Keep the published provider and request method unchanged.
user- 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- First-page size. Ignored when `cursor` is supplied (the cursor's size wins).
cursor- Opaque pagination cursor from a prior response's `next_cursor`.
condition- Combo condition id(s), comma-separated (at most 20 distinct values). `condition_id` / `conditionId` are accepted aliases.
status- 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- `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.
sort_direction- `ASC` or `DESC` (default `DESC`).
updated_after- 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.
updated_before- 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.
Terminal · cURLcurl \ 'https://api.openany.si/v1/agent-apis/polymarket/v2/positions/combos?limit=2&user=0x17eC161f126e82A8ba337f4022d574DBEaFef575' \ -X GET \ -H "Authorization: Bearer $OPENANY_API_KEY" \ -H 'Content-Type: application/json'Check the response
Sample response · Documented HTTP 200
Sample response{ "data": [], "pagination": { "has_more": false, "limit": 2, "next_cursor": null, "offset": 0 } }
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.