Polymarket — List account activity

List account activity 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
Required; the feed is user-anchored. This execution profile requires an explicit non-null value. The original optional/nullable OpenAPI declarations remain in officialOperation.
Optional parameters (11)
Page size; default 100, max 1000, past-cap rejected.
Opaque cursor from a prior response's `next_cursor`; binds the sort direction it was minted under.
Activity type(s), comma-separated. Accepted values: `TRADE`, `SPLIT`, `MERGE`, `REDEEM` (automatic redemptions included), `CONVERSION`, `MIGRATION`, `REWARD`, `YIELD`, `MAKER_REBATE`, `TAKER_REBATE`, `REFERRAL_REWARD`, `DEPOSIT`, `WITHDRAWAL`, `TIP`. Any other value is rejected with `400`. Omitted, the feed returns every type except `TIP`. `DEPOSIT` and `WITHDRAWAL` rows are returned only with `exclude_deposits_withdrawals=false`. Under its default (`true`) they are dropped even when named here, so `type=DEPOSIT` or `type=WITHDRAWAL` alone returns an empty page. `TIP` is **opt-in**: it is never in the default set, so it is only returned when you name it here. A tip is a user↔user pUSD transfer that is not a trade-settlement leg; `size` is the amount and `side` carries the direction (`IN` received / `OUT` sent).
Condition id(s), comma-separated (at most 20 distinct values). `condition_id` / `conditionId` are accepted aliases.
Gamma event id(s), comma-separated (at most 20 distinct values); resolves to the events' markets. Mutually exclusive with `condition`.
BUY or SELL.
Window start on `block_timestamp`, epoch seconds (inclusive). Omitted or `0` floors to three years back; pass `start=1` for full history.
Window end, epoch seconds (inclusive); omitted or `0` means now plus one day.
Only `TIMESTAMP` is supported (v2 pages by keyset).
`ASC` or `DESC` (default). The keyset seeks in the chosen direction; the minted cursor binds it, so pass it consistently when paging.
Defaults to `true`, which drops `DEPOSIT` and `WITHDRAWAL` rows from the page, including when `type` names them. Pass `false` to include them.

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 account activity with your agent

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