Skip to main content
POST
/
exchange
No-op
curl --request POST \
  --url https://api.hyperliquid.xyz/exchange \
  --header 'Content-Type: application/json' \
  --data '
{
  "action": {
    "type": "noop"
  },
  "nonce": 1705234567890,
  "signature": {
    "r": "0x0000000000000000000000000000000000000000000000000000000000000000",
    "s": "0x0000000000000000000000000000000000000000000000000000000000000000",
    "v": 27
  },
  "vaultAddress": null
}
'
{
  "status": "<string>",
  "response": {}
}
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.
Performs a no-operation action. Useful for testing signature authentication or consuming rate limit weight without side effects.
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 action object containing:
    • type (string) — Must be "noop"
  • nonce (number, required) — Current timestamp in milliseconds (must be recent)
  • signature (object, required) — EIP-712 signature of the action

​
Optional parameters

  • vaultAddress (string, optional) — Address when trading on behalf of a vault or subaccount

​
Returns

Returns an object with the action status:
  • status — "ok" if request processed
  • response — Contains action result data

​
Example request

cURL
curl -X POST https://api.hyperliquid.xyz/exchange \
  -H "Content-Type: application/json" \
  -d '{
    "action": {"type": "noop"},
    "nonce": 1234567890123,
    "signature": {...}
  }'

​
Use case

  • No-op — Performs a no-operation action. Useful for testing signature authentication or consuming rate limit weight without side effects.
Always ensure your system clock is synchronized. Nonce must be within a reasonable time window of the current server time or the request will be rejected.

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

​
vaultAddress
string | null

Address when trading on behalf of a vault or subaccount (optional)

Response

200 - application/json

Action result

​
status
string

Request status

​
response
object

Action response data

Last modified on February 17, 2026