Skip to main content
POST
/
exchange
Modify a sub-account
curl --request POST \
  --url https://api.hyperliquid.xyz/exchange \
  --header 'Content-Type: application/json' \
  --data '
{
  "action": {
    "type": "subAccountModify",
    "subAccountUser": "0x1442ad477ded1b0028b57621aa7b6f7eadb8f568",
    "name": "Strategy A"
  },
  "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 subAccountModify action renames a sub-account under your master account.
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 sub-account-modify action:
    • type (string) — Must be "subAccountModify".
    • subAccountUser (string) — The sub-account address to modify.
    • name (string) — The new sub-account name (1-16 characters).
  • nonce (number, required) — Current timestamp in milliseconds.
  • 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, with type "default".

​
Example request

curl -X POST https://api.hyperliquid.xyz/exchange \
  -H "Content-Type: application/json" \
  -d '{
    "action": {
      "type": "subAccountModify",
      "subAccountUser": "0x1442ad477ded1b0028b57621aa7b6f7eadb8f568",
      "name": "Strategy A"
    },
    "nonce": 1234567890123,
    "signature": {...}
  }'

​
Response example

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

​
Use cases

  • Organize sub-accounts — Give sub-accounts meaningful names
  • Strategy labeling — Name sub-accounts by strategy or desk
  • Account management — Maintain a clear sub-account structure

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

​
expiresAfter
integer

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

Response

200 - application/json

Sub-account modify result

​
status
string

Request status

​
response
object
Last modified on June 24, 2026