Skip to main content
POST
/
exchange
User outcome (split / merge / negate outcome shares)
curl --request POST \
  --url https://api.hyperliquid.xyz/exchange \
  --header 'Content-Type: application/json' \
  --data '
{
  "action": {
    "type": "userOutcome",
    "splitOutcome": {
      "outcome": 0,
      "amount": "1"
    }
  },
  "nonce": 1705234567890,
  "signature": {
    "r": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef",
    "s": "0xfedcba0987654321fedcba0987654321fedcba0987654321fedcba0987654321",
    "v": 27
  }
}
'
{
  "status": "ok",
  "response": {
    "type": "default"
  }
}
You can only use this endpoint on the official Hyperliquid public API. It is not available through Chainstack, as the open-source node implementation does not support it yet. See Hyperliquid methods for the full availability breakdown.
This endpoint requires signature authentication. See our comprehensive Authentication via Signatures guide for implementation details.
The userOutcome action manually splits or merges outcome-market shares to convert between quote tokens and Yes/No shares. Outcome markets are binary (Yes/No) prediction markets on Hyperliquid. A single userOutcome action carries exactly one of four operations: splitOutcome, mergeOutcome, mergeQuestion, or negateOutcome.
Get your own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

​
Required parameters

  • action (object, required) — The user outcome action. Set type to "userOutcome" and include exactly one of the following operations:
    • splitOutcome — Split X quote tokens into X Yes and X No shares of an outcome. Fields: outcome (number), amount (string, e.g. "123.0").
    • mergeOutcome — Merge X Yes and X No shares of an outcome into X quote tokens. Fields: outcome (number), amount (string or null, where null means the maximum available).
    • mergeQuestion — Merge X Yes shares from each outcome associated to the same question into X quote tokens. Fields: question (number), amount (string or null, where null means the maximum available).
    • negateOutcome — Convert X No shares from an outcome associated with a question into X Yes shares of every other outcome associated with the question. Fields: question (number), outcome (number), amount (string).
  • nonce (number, required) — Current timestamp in milliseconds (must be recent).
  • signature (object, required) — EIP-712 signature of the action.

​
Optional parameters

  • expiresAfter (number, optional) — Timestamp in milliseconds after which the request is rejected.

​
Returns

Returns an object with the action status:
  • status — "ok" if the request was processed.
  • response — Contains operation details:
    • type — "default".

​
Example request

# Split outcome: split 1 quote token into 1 Yes and 1 No share of outcome 0
curl -X POST https://api.hyperliquid.xyz/exchange \
  -H "Content-Type: application/json" \
  -d '{
    "action": {
      "type": "userOutcome",
      "splitOutcome": {"outcome": 0, "amount": "1"}
    },
    "nonce": 1234567890123,
    "signature": {...}
  }'

​
Response example

{
  "status": "ok",
  "response": {
    "type": "default"
  }
}

​
Use cases

  • Provide outcome liquidity — Split quote tokens into Yes and No shares to make markets on both sides
  • Redeem shares — Merge matched Yes and No shares back into quote tokens
  • Manage positions across a question — Merge or negate shares across the outcomes of a single question

Body

application/json
​
action
object
required

User outcome action. Provide exactly one of splitOutcome, mergeOutcome, mergeQuestion, or negateOutcome alongside the type.

​
nonce
integer
required

Current timestamp in milliseconds

​
signature
object
required

EIP-712 signature of the action with r, s, v components

​
expiresAfter
integer

Timestamp in milliseconds after which the request is rejected (optional)

Response

200 - application/json

User outcome result

​
status
string

Request status

​
response
object
Last modified on June 24, 2026