| Term | Meaning |
|---|---|
| HIP-4 | Hyperliquid’s outcome markets. A market usually resolves fully YES or NO, but can resolve to a fraction, so each side pays part. |
| Market | One HIP-4 outcome (outcome_id) with a YES and a NO side. |
| Leg | One outcome and one side: { "outcome_id": "1209", "side": "YES" }. Two or more legs make a combo. |
| Combo | One position on several legs. It pays its payout times the product of its legs’ results: all of it if every leg wins, nothing if one loses, part if a leg resolves to a fraction (each leg pays result_numerator / result_denominator; see Settlement). The contracts and the signing domain (TotalisParlay) still call it a parlay. |
| Taker | The account that creates an RFQ and accepts a quote. For a cash-out, the position’s owner. |
| Maker | A market maker (maker_id) that quotes, confirms and backs positions from its maker vault. |
| RFQ | Request for quote. ENTRY prices new legs for a stake; CASHOUT prices an existing position. |
| Quote | A maker’s unsigned offer on one RFQ: entry terms (a payout), or sell_back terms (a price). |
| Acceptance | The record of one accept on one quote, named by the accept’s Idempotency-Key (acceptance_id). A quote has at most one. |
| Confirm | The maker’s answer to an acceptance before its deadline, 2 seconds after the accept: CONFIRM with a signature, or DECLINE. |
| Position | A filled trade on-chain: legs, stake, payout, owner and backing maker. An entry position’s position_id is its quote_id. |
| Stake, payout | What the taker pays, before the entry fee (taker_fee_bps); what the position pays if every leg wins, before the profit fee (fee_bps). |
| Cash-out | Selling an open position back to the maker that backs it (sell_back). Only that maker bids. |
| Leg state | A cash-out RFQ’s hash of every leg’s on-chain state (leg_state). A cash-out lands only while the position’s legs still hash to it; otherwise the trade reverts. See Price a cash-out. |
| Settlement, claim | Grading a resolved position, then paying its winnings into the owner’s vault balance. Totalis runs both. |
| Operation | One on-chain action Totalis relays for you, with a status (operation_id, OPERATION_UPDATED). |
| Vault | The Totalis contract on HyperEVM that holds USDC and every position (vault_address). |
| Maker vault | The USDC that backs a maker’s positions: its deposits, plus takers’ stakes held while their positions are open. Separate from the maker owner’s own vault balance. |
| Free collateral | What a maker vault can still back: free_collateral in Get maker capital. |
| Collateral reduction | A job that lowers a maker’s requirement to what its open positions can lose together. See Maker collateral. |
| Totalis balance | Your wallet’s USDC on HyperEVM plus your free vault balance. |
| Wallet | The account’s wallet. It approves the account’s keys and signs its trades. wallet_kind on GET /v1/me is EMBEDDED for a wallet embedded in the Totalis app, and EXTERNAL for one that signs in on a partner’s site, including a wallet embedded in the partner’s own app. Only EMBEDDED wallets have their vault cash swept to HyperCore in the background. |
| Wallet session | A bearer token from a wallet’s Sign-In with Ethereum, bound to the origin it signed in from: the Totalis app’s origin for a maker, or a partner’s registered origin. It lasts at most 30 days and ends after 7 idle days. See Your users’ own wallets. |
| Vault agent | A key the account’s wallet approved with an AgentGrant. Until the grant ends it signs the account’s entry accepts, cash-outs and moves of vault cash back to the account. See Vault agents. |
| Partner | A builder whose server admits wallets and whose frontend signs them in, with keys Totalis issues. See Build on Totalis. |
| Admission | A partner’s server letting a consenting wallet create its account. The first partner to admit a wallet keeps it. |
| Builder code | A code on an RFQ that attributes it to a partner (builder_code). See Builder codes. |
| Deployment | The chain, vault, current fees and USDC domain that quotes and signatures use (Get deployment). Trade messages sign against the vault; USDC authorizations sign against the USDC domain. |
| Cursor | Your place in the WebSocket. Send it back to resume. |
Resources
Glossary
Every term the Hyperliquid API uses, from leg and RFQ to acceptance, operation, cursor and collateral reduction.
Was this page helpful?

