Skip to main content
GET
Get actions by transaction hash
Use this endpoint to inspect an indexed Polymarket trade or combo transaction. Given a transaction hash, it returns a decoded summary and every fill recorded for that transaction. The top-level sentence field gives you a ready-to-read description, for example:
Buy 5 Yes for $3.9 in Will France win on 2026-06-30?
Treat sentence as display text. Use actions or comboActions for calculations. The actions array then lists each individual fill. One transaction often contains several, because a single trade can be matched against multiple counterparties. Each fill shows who acted (traderAddress), the size (shares), the price (decimal 0 to 1), the usdcSize (USDC value), and whether they were the MAKER or TAKER (liquidityRole).
You can get a transaction hash from the Get Trader Activity endpoint. Every activity item includes a txHash you can feed straight into this endpoint.
The txHash must be a 32-byte hex hash. A malformed value returns HTTP 400 with "Invalid txHash format". A well-formed hash that isn’t indexed returns HTTP 200 with data: null. See Errors.

Regular trades and combo trades

The top-level sourceType tells you which kind of transaction you’re looking at:
  • TRADE: a regular order fill. The individual fills are in actions, and comboActions is null.
  • COMBO: a combo (parlay) trade that bundles several market outcomes into one position. The fills are in comboActions, and actions is null. Since a combo spans more than one market, the top-level marketId and marketSlug are also null. The sentence reads like Buy Combo position for $4.999993.
Each entry in comboActions is one trader’s fill of a combo position. It carries a comboPositionId and a legs array listing the market outcomes in the parlay. The response schema on this page describes every field. To see both shapes, switch the sample response between Regular trade and Combo trade.

Authorizations

Authorization
string
header
required

Paste your Orbscan API key here. The Bearer prefix is added automatically.

Path Parameters

txHash
string
required

The transaction hash to decode.

Example:

"0xbf15dbfb9d3b8b1f5210a582ca78deb73bf77372cb43d8e15edb323750461b1c"

Response

Returns the decoded transaction. A well-formed hash that is not indexed returns data: null.

message
enum<string>
required
Available options:
OK
Example:

"OK"

status_code
enum<string>
required
Available options:
1
Example:

"1"

data
Regular trade · object
required

The decoded transaction, or null when the hash is well-formed but no indexed action matches it.