Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

outcomeMetaByInstrument

On-chain trading parameters for one Outcome instrument: name, assets, fee curve, price tick, resolution status, and channel. Fields are camelCase. For event titles, slugs, and live prices, use outcomeMeta.

POST/infotype outcomeMetaByInstrument

Read on-chain trading params (tick, fee curve, resolution status) for one Outcome instrument.

Not this?
  • infooutcomeMeta — when you need event titles, slugs, or a list of markets
Note
Outcome markets only.
Request body
instrumentIdinteger · int64required

Outcome instrument id.

typestringrequired
Request example
curl -X POST https://rpc.txflow-testnet.xyz/info \
  -H "Content-Type: application/json" \
  -H "x-api-version: 2026-08-16" \
  -d '{
  "type": "outcomeMetaByInstrument",
  "instrumentId": 9001
}'
Try it
POST https://rpc.txflow-testnet.xyz/info
Response · OutcomeInstrument 200
codeinteger

`0` on success.

dataOutcomeInstrument
exponentstring

Fee-curve exponent. Wire value is a decimal string (for example `"1"`).

feeRatestring

Outcome fee-curve base rate.

indexinteger · int64

Instrument external id (same as `instrumentId`).

makerRebateRatestring
namestring
priceTickstring
szDecimalsinteger · int64
tokensinteger · int64[]

Base and quote asset ids.

exchangeIdinteger · int32nullable

Channel id. `0` or omitted is the default platform channel.

resolutionStatusstringnullable

`Prepared` or `Resolved`. Defaults to `Prepared` when unset on the instrument.

successboolean

`false` on error, with `code` set and the text in `message` instead of `data`.

Response example
{
  "success": true,
  "code": 0,
  "data": {
    "name": "",
    "szDecimals": 0,
    "tokens": [
      0
    ],
    "index": 0,
    "priceTick": "0",
    "feeRate": "",
    "exponent": "",
    "makerRebateRate": "",
    "resolutionStatus": ""
  }
}