Skip to main content
POST
/
exchange
Link a staking user (initiate or finalize)
curl --request POST \
  --url https://api.hyperliquid.xyz/exchange \
  --header 'Content-Type: application/json' \
  --data '
{
  "action": {
    "type": "linkStakingUser",
    "signatureChainId": "0x66eee",
    "hyperliquidChain": "Mainnet",
    "user": "0x1442ad477ded1b0028b57621aa7b6f7eadb8f568",
    "isFinalize": false,
    "nonce": 1705234567890
  },
  "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 linkStakingUser action links a staking account and a trading account so that staking is attributed for fee discounts. The link is a two-step flow: the trading user initiates the request (isFinalize: false), then the staking user finalizes the permanent link (isFinalize: true). This is a user-signed EIP-712 action.
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 link-staking-user action:
    • type (string) — Must be "linkStakingUser".
    • signatureChainId (string) — Chain ID in hex used for EIP-712 signing.
    • hyperliquidChain (string) — "Mainnet" or "Testnet".
    • user (string) — Target account address. When the trading user initiates, this is the staking account address; when the staking user finalizes, this is the trading account address.
    • isFinalize (boolean) — false to initiate (trading user), true to finalize the permanent link (staking user).
    • nonce (number) — Timestamp in milliseconds, equal to the envelope nonce.
  • nonce (number, required) — Current timestamp in milliseconds.
  • signature (object, required) — EIP-712 signature of the action.

​
Returns

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

​
Example request

curl -X POST https://api.hyperliquid.xyz/exchange \
  -H "Content-Type: application/json" \
  -d '{
    "action": {
      "type": "linkStakingUser",
      "signatureChainId": "0x66eee",
      "hyperliquidChain": "Mainnet",
      "user": "0x0000000000000000000000000000000000000000",
      "isFinalize": false,
      "nonce": 1234567890123
    },
    "nonce": 1234567890123,
    "signature": {...}
  }'

​
Response example

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

​
Use cases

  • Attribute staking for fee discounts — Link a staking account to a trading account
  • Separate custody and trading — Keep staked funds and trading funds in different accounts
  • Two-step linking — Initiate from the trading user, finalize from the staking user

Body

application/json
​
action
object
required
​
nonce
integer
required

Current timestamp in milliseconds

​
signature
object
required

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

Response

200 - application/json

Link staking user result

​
status
string

Request status

​
response
object
Last modified on June 24, 2026