Wallet Activity (Polymarket)
Complete activity feed for a Polymarket wallet — every TRADE, SPLIT, MERGE, REDEEM, CONVERSION, and REWARD event in one clean, consistent schema.
/v2/polymarket/activityQuery Parameters
Wallet address — must match ^0x[a-fA-F0-9]{40}$.
Optional. Filter to a single event type: TRADE | SPLIT | MERGE | REDEEM | CONVERSION | REWARD.
Optional. Filter to a single market by condition_id.
Optional. Page size (default 100, max 500).
Optional. Page offset (default 0).
Response Schema
Wallet address (lowercased).
Page size returned (max 500).
Page offset.
Number of activity rows returned in this page.
True when count == limit, indicating another page may exist. Use offset += limit to fetch the next page.
Per-event records with a clean, consistent snake_case schema.
Polymarket proxy wallet that performed the action.
Market condition ID.
TRADE | SPLIT | MERGE | REDEEM | CONVERSION | REWARD.
Outcome label (e.g. "Yes").
Outcome index in the market.
USDC amount of the event.
Taker fee paid for this event in USDC.
Bonus/incentive amount, if any.
Polygon tx hash.
Unix seconds of the event.
Source and cache metadata.
Data source identifier.
hit | miss — whether the response was served from the low-latency cache or freshly resolved.
Cache window in seconds.
Error Responses
All errors return the same envelope. The code field is stable and programmatically branchable; error and message are human-readable. errors[] is present only on validation failures with field-level detail. See the full error code reference →
Always `false` on error responses.
Short, human-readable title (e.g. 'Invalid API Key.').
Human-readable explanation for the error. Safe to surface in UIs.
Stable, hierarchical machine-readable code (e.g. 'validation.invalid_enum'). Use for programmatic handling.
Link to this code's entry in the Error Reference.
Optional. Present only on validation failures with field-level detail.
Name of the offending parameter.
Field-level machine code.
Human-readable explanation.
Authentication
API Key
To secure your requests, we strongly recommend passing your API key via the X-API-Key header. This prevents sensitive keys from being exposed in access logs or browser history.
X-API-Key: pmx_test_5e8f...Rate Limits
API rate limits are enforced based on the tier associated with your API key. Limits are tracked on two dimensions: requests per second and requests per month. Each completed request counts toward the global monthly quota. Separate endpoint-group monthly limits (matched markets, arbitrage, EV) only advance when the response body has success: true.
Usage is returned on responses via headers such as:
X-RateLimit-Limit-Second: 10X-RateLimit-Remaining-Second: 9X-RateLimit-Limit-Month: 1000X-RateLimit-Remaining-Month: 842Example (endpoint-group, when applicable)X-RateLimit-Limit-Arb-Month: 500X-RateLimit-Remaining-Arb-Month: 412If you exceed a rate limit, the API returns a 429 status with a Retry-After header indicating when you can resume.
Request
Live API Key
Parameters
Response
—Click EXECUTE to send a request →