Polymarket trade history

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

BlockRun

View Polymarket trades | BlockRun

View a page of recent Polymarket trades with no search or setup. See each market and answer choice, amount traded, recorded price, dollar value and time; fees appear when provided.

You receive

Receive one page of recorded Polymarket fills. You can start without a wallet, market identifier or search term and choose how many records to request. Each row connects a market and outcome with its recorded trade direction, share quantity and raw blockchain units, historical price on a 0–1 scale, USD value, maker and counterparty addresses, order and transaction hashes, and trade time. Read fees when provided, keeping a recorded zero distinct from a missing fee. The response also gives the page count and whether more records are indicated. Ask your Agent to arrange these details for comparing fills or tracing an order or transaction. Several rows can share the same transaction or order identifier, so a row count is not a count of unique transactions.

Start with your task

Show up to three of the most recent Polymarket trades from the last 24 hours. For each, name the market and answer choice, amount traded, recorded price, dollar value and time. Include a fee only when one is shown, and keep every trade separate.

What to know

The default global first page uses the source’s last-24-hours query window. Each page is partial historical data. Recorded prices do not establish a current executable quote, and fills do not establish present holdings or trading profit. Complete coverage and refresh delay are unspecified.

Inputs & outputs

Inspect the current inputs, availability, and maximum charge before starting.

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
Page size and source query settings`queryParams`	`object`	Optional	Put source query settings directly here; the shown task uses limit=3. The source permits a limit from 1 to 500 and defaults to 100, using descending global trades with an initial last-24-hours window. No wallet or market ID is required for this task. For another scope, the matching source documents market/token, maker-wallet, time, minimum USD value, hash and builder filters; confirm the chosen settings first. Time bounds use Unix seconds; wallet filtering matches the maker side.
Optional nested query container`queryParams.query`	`object`	Optional	This native open object is forwarded unchanged. The supplier’s URL query controls belong directly in queryParams; omit this nested container for the shown recent-page task. It does not flatten nested values into those controls.

View raw JSON

{
  "type": "object",
  "required": [],
  "properties": {
    "queryParams": {
      "type": "object",
      "properties": {
        "query": {
          "type": "object",
          "required": [],
          "properties": {}
        }
      }
    }
  },
  "additionalProperties": false
}

Result schema

Output fields have not been documented yet.

Additional notes

Read quantities and money separately

Normalized shares equal raw blockchain share units divided by 1,000,000. Read USD trade value and any USD fee separately: fee inclusion in the trade value, the payer and the calculation are unspecified. Retain the recorded 0–1 price as supplied; its independent currency and probability interpretation are unspecified.

Keep fills, participants and IDs together

One transaction can contain several fills, and an order can have fills across transactions. Keep separate rows when grouping by hash; a row count or an unqualified sum is not a verified transaction total. Keep the buy/sell direction separate from the market outcome and retain the maker and counterparty addresses. The source does not explicitly define which participant’s action the direction code expresses, so that code alone cannot identify a selected wallet’s action.

Keep the query scope with the page

The official trade documentation specifies 1–500 records per page, with a default of 100. Global requests without a market or wallet filter use newest-first ordering, and the first page defaults to a last-24-hours query window.

Trade timestamps use Unix seconds and refer to recorded events. The count describes fills in this page. A more-data flag and an actual cursor indicate source continuation, but do not fetch another page automatically. The source describes wider time ranges as global pagination goes back, so the initial 24-hour window should not be applied to every later page.

Ask for recent trades
No search or preparation is needed. You can request recent trades across Polymarket right away; the first page covers the previous 24 hours.
Get connected
Copy a simple request
Copy the request below and send it to your connected AI. No extra information is needed.
Show up to three of the most recent Polymarket trades from the last 24 hours. For each, name the market and answer choice, amount traded, recorded price, dollar value and time. Include a fee only when one is shown, and keep every trade separate.
Know what the list covers
Each page shows only part of the history. These are past trades, not live prices or an account’s current balance or profit. A fee not shown is different from a fee recorded as $0.