Amounts, prices and volume | Whalehunt | Polymarket Realtime Data

Signed order terms, requested fills, provisional estimates and receipt results are different facts.

Fields	Meaning	Use
`signedMakerAmount`, `signedTakerAmount`, `limitRatio`	Signed terms	A limit, not an average execution price
`requestedFillMakerAmount`, `requestedFeeArgument`	Call arguments	Do not count as executed amounts or actual fees
`calculation`	Provisional rule-based result or unavailable reason	Preserve the status; unavailable is not zero
Execution `amounts`	Normalized receipt actuals	Account for identity and occurrence canonicality

Exact integers and units

Amounts and token IDs are decimal strings. Store them as strings or arbitrary-precision integers. JavaScript Number and binary floating point can lose precision.

grossCash, shares, fee and netCash use raw asset units. Obtain decimal scaling from verified asset configuration. As a conditional arithmetic example, with a scale of six, "1250000" means 1.25 asset units. The example does not establish a universal scale.

Multiple makers

One call can include several maker orders and a taker. Signed ratios are not a shared average execution price. Fees and rounding cannot be recovered reliably by dividing arbitrary pending arguments. Even provisional_maker_taking remains provisional.

Maker and taker executions can describe the same exchange. Do not add every fill.execution as independent market volume. resource_ids identifies shared economic resources, not additional trades. When the available fields do not support your metric, keep that result unavailable.

Redelivery and a new assessment revision are also not new volume. A revision changes the state of an existing entity. See event fields.