Configs

The configs query returns all coin definitions and contract configurations available on the exchange. Use it to resolve contract IDs for the a field, read the decimal scales that convert display values to the raw integers the wire protocol expects, obtain tick and step sizes for validation, and inspect leverage tiers for margin calculations.

This endpoint is the authority

Three sources describe the API, and they are not interchangeable:

Source	Defines	Never use it for
The endpoint reference pages	Structure — field names, types, required/optional, enum sets	Current parameter values
`configs` (this endpoint)	Current trading parameters — scales, tick/step, leverage, tiers, fees, limits	—
Examples anywhere in these docs	Nothing. They illustrate shape only	Any business fact: scales, IDs, contract names, leverage, fees

Every numeric value in every example on this site is illustrative and must not be used to build an order. Resolve the real value from configs at runtime, for the exact contract you are trading.

Scales are per contract and are frequently 0. A contract with priceScale: 0 takes the display price unchanged; one with qtyScale: 0 takes whole units only. Reusing another contract’s scale, or a scale copied from documentation, misprices an order by a factor of ten or more without any error from the server. Read priceScale and qtyScale from the contract object you are about to trade — every session, never cached across a config change.

Stop conditions

An automated client must halt and surface the problem rather than improvise when any of the following holds. Substituting a different contract is never correct.

The target contract name is absent from the response.
More than one contract shares the target name.
The contract object is missing any field the order path needs: priceScale, qtyScale, tickSize, stepSize, minTradeNtl, or tiers.
The matched contract’s status is anything other than "Active".

There is no version or snapshot identifier on this response. You cannot currently prove that a quote, a validation pass, and a signature all used the same configuration. The only change signal available is the version field pushed by the config WebSocket channel — subscribe to it, and re-fetch configs and re-validate any unsigned order when the version changes. Treat a configuration change between validation and signing as a reason to abort and revalidate.

Request

{"type": "configs", "marketDeployerId": 0}

string

required

Must be "configs".

integer

Filter results by market deployer. Use 0 or omit to return configuration for all deployers. Pass a positive integer to restrict results to a specific deployer.

Response

{
  "type": "configs",
  "marketDeployerIdFilter": 0,
  "coins": [
    { "coinId": 1, "name": "USDC", "szDecimals": 6, "isMargin": true, "status": "Active" },
    { "coinId": 3, "name": "BTC", "szDecimals": 8, "isMargin": false, "status": "Active" },
    { "coinId": 4, "name": "ETH", "szDecimals": 8, "isMargin": false, "status": "Active" }
  ],
  "contracts": [
    {
      "contractId": 1,
      "marketId": 1,
      "marketDeployerId": 1,
      "name": "BTC-USDC",
      "baseCoinId": 3,
      "quoteCoinId": 1,
      "tickSize": "1",
      "stepSize": "1",
      "priceScale": 0,
      "qtyScale": 4,
      "defaultLeverage": "20",
      "defaultTakerBps": 5,
      "defaultMakerBps": 2,
      "icon": "",
      "fundingInterval": 3600,
      "minTradeNtl": "1",
      "status": "Active",
      "tiers": [
        { "upperBound": "2000000000000", "maxLeverage": "40", "imBps": 250, "mmBps": 125 },
        { "upperBound": "4000000000000", "maxLeverage": "20", "imBps": 500, "mmBps": 250 },
        { "upperBound": "9223372036854775807", "maxLeverage": "10", "imBps": 1000, "mmBps": 500 }
      ]
    },
    {
      "contractId": 3,
      "name": "EXAMPLE-USDC",
      "priceScale": 2,
      "qtyScale": 2,
      "status": "Delisted"
    }
  ]
}

The response mixes tradeable and untradeable contracts. The second entry above is Delisted — it is returned in full, with a complete and plausible set of parameters, and nothing else marks it as unusable. Filter on status before anything else.Note also that priceScale is 0 for the contract above: its raw price equals its display price. Scales differ per contract and 0 is common.

Discovery and filtering

string

Whether the contract is tradeable. "Active" means it is; "Delisted" means it is not. Treat any value other than "Active" as untradeable — the set of values is not closed, so fail safe rather than enumerating.This is the primary filter. A delisted contract is returned with a complete parameter set and is indistinguishable from a live one on any other field.

Coin status is independent of contract status. A coin stays Active after its contract is delisted, so a coin being Active tells you nothing about whether you can trade it. Always check the contract.

Resolve a contract in this order:

Filter to status Active

Discard every contract whose status is not exactly "Active".

Match on name

Find your target by name. Never select by contractId — IDs are server-assigned and do not map to any fixed pair.

Stop if the result is not exactly one contract

Zero matches, or more than one, is a stop condition. Do not fall back to another contract.

Read that contract's own parameters

Take priceScale, qtyScale, tickSize, stepSize and tiers from the matched object only.

Fee defaults

integer

Contract-level default taker fee rate in basis points. The rate actually applied to your account resolves through the fee hierarchy — read effectiveTakerBps from userAccount for the value in force.

integer

Contract-level default maker fee rate in basis points, resolved the same way as defaultTakerBps.

Notional, and the limits enforced on it

Order validation works on notional, not on price or size alone. Notional is an integer in the settlement coin’s raw units — the quote coin’s szDecimals:

notional = price_raw × size_raw × notionalScaleMultiplier

string

The factor that converts price_raw × size_raw into the settlement coin’s raw units. It is derived, not independent:

notionalScaleMultiplier = 10 ^ (quoteCoin.szDecimals − priceScale − qtyScale)

Contract creation enforces priceScale + qtyScale ≤ quoteCoin.szDecimals, so the exponent is never negative. Read the value from this response rather than recomputing it.

string

Minimum notional, in settlement-coin raw units. An order whose notional is below this is rejected with notional below minTradeNtl.

string

Maximum notional for a single order, in settlement-coin raw units, compared against that order’s own price × size. Exceeding it is rejected with notional exceeds maxPositionNotional.

integer

How far a limit order’s price may deviate from the mark price, in basis points: the order is rejected with price exceeds priceBandBps when |price − mark| > mark × priceBandBps / 10000.The band is not applied when priceBandBps is 0, when no mark price has been published yet, or to market orders.

Market orders are not price-band checked. Because you supply the execution price yourself, nothing bounds how far a market order may cross the book — a mistyped price will sweep it. What limits the damage is the margin pre-check, which charges the full difference between your submitted price and the mark price without dividing by leverage. Compute the market price from the mark price and your account’s slippage allowance, and validate it yourself before signing.

Worked example

Using a contract with priceScale: 0, qtyScale: 4, notionalScaleMultiplier: "100", settled in a coin with szDecimals: 6 — buying 0.01 at a display price of 70000:

Step	Value
`price_raw` = `70000 × 10^0`	`70000`
`size_raw` = `0.01 × 10^4`	`100`
`notional` = `70000 × 100 × 100`	`700000000`
In display terms: `700000000 / 10^6`	`700.00` — the expected `70000 × 0.01`

Check that notional against minTradeNtl and maxPositionNotional before signing; both are expressed in the same raw units.

Fields returned but not specified

The response carries the fields below. Their semantics are not part of the published contract, so do not build order sizing, margin, or risk logic on them. They are listed here so that an automated client can recognise and ignore them rather than infer a meaning from the name.

Field	Scope
`marketSlippageBps`	contract — see the warning below
`liquidationFeeBps`, `frozenMarginBps`, `frozenFeeBps`, `autoDeleverageLineBps`	contract
`marketId`, `flags`, `listingTime`	contract
`chainFeeAccountId`, `chainFeeShareBps`	top level
`allIsMarginCoins`	top level — the coin IDs usable as margin
`shareMarginGroups`	top level — empty unless share groups are configured; group definitions come from `shareGroupState`
`marketDeployers[]`	top level — `deployerAccountId`, `liquidatorAccountId`, `deployerTakerBps`, `deployerMakerBps`, and `settleCoinId` (the deployer’s settlement coin)

marketSlippageBps exists at two different scopes with the same name and different meanings. The one in this response is a contract field. The one returned by userAccount, and written by updateSlippageSetting, is an account setting scoped to (account, market deployer) and is the one that governs the price you compute for a market order. Do not substitute one for the other.

Treat any field not described on this page as reserved. A future response may add fields; ignore unknown keys rather than failing, and do not rely on a field’s continued presence until it is specified here.

Contract Fields

integer

The unique contract identifier. Use this as the a field when placing, modifying, or canceling orders.

string

Human-readable contract name (e.g. "BTC-USDC").

string

Minimum price movement expressed as a raw integer string. All order prices must be multiples of this value.

string

Minimum quantity movement expressed as a raw integer string. All order quantities must be multiples of this value.

integer

Decimal exponent for prices. Divide any raw price by 10^priceScale to get the human-readable display value.

integer

Decimal exponent for quantities. Divide any raw quantity by 10^qtyScale to get the human-readable display value.

string

The initial leverage applied to new positions on this contract.

string

URL of the contract’s icon, or an empty string when none is set — never null. The host is not guaranteed and varies between contracts, so treat the value as an opaque URL: do not derive other URLs from it, and do not assume it is served from an Upsidemax domain.

integer

Funding settlement interval in seconds; funding settles once per interval. The value comes from a fixed set: 3600 (1h), 7200 (2h), 14400 (4h), or 28800 (8h).

string

Minimum notional value per trade, expressed as a raw integer string.

Tier[]

Leverage tier schedule for this contract. Each tier applies up to upperBound position size.

Show Tier fields

string

Maximum position size (raw) to which this tier applies. The highest tier uses "9223372036854775807" (max int64) as a sentinel for “no upper limit.”

string

Maximum leverage allowed for positions up to upperBound.

integer

Initial margin rate in basis points (e.g. 100 = 1%).

integer

Maintenance margin rate in basis points. Positions are liquidated when equity falls below this threshold.

Overview

Market Data

Account

Orders

History

This endpoint is the authority

Stop conditions

Request

Response

Discovery and filtering

Fee defaults

Notional, and the limits enforced on it

Worked example

Fields returned but not specified

Contract Fields

​This endpoint is the authority

​Stop conditions

​Request

​Response

​Discovery and filtering

​Fee defaults

​Notional, and the limits enforced on it

​Worked example

​Fields returned but not specified

​Contract Fields

This endpoint is the authority

Stop conditions

Request

Response

Discovery and filtering

Fee defaults

Notional, and the limits enforced on it

Worked example

Fields returned but not specified

Contract Fields