Sign in
Trading

Submit a Hyperliquid order through an active agent session

Requires an agent JWT for the calling agent. Orders are rate-limited, idempotency-protected, scoped to an active Hyperliquid session, rechecked against adapter asset support, evaluated against leverage/per-order/daily-spend policy before signing, and audited on both success and policy rejection.

post/trade/hyperliquid/order

Headers

X-Steward-Request-Timestampstring

Unix seconds, Unix milliseconds, or HTTP/ISO timestamp. Sensitive mutating routes require this or X-Steward-Request-Expires-At when request-expiry or request signatures are enforced.

X-Steward-Request-Expires-Atstring

Unix seconds, Unix milliseconds, or HTTP/ISO expiry time. Sensitive mutating routes require this or X-Steward-Request-Timestamp when request-expiry or request signatures are enforced.

X-Steward-Signaturestring

Authorization signature for sensitive mutating routes when STEWARD_REQUIRE_AUTH_SIGNATURE=true or production enforcement is enabled. Use v1=<hmac-sha256> or p256=<signature>.

X-Steward-Signing-Key-Idstring

Tenant request-signing key id used to select a managed HMAC signing key. Required when signing with a managed tenant key; omit only for static or app-client signing secrets.

Idempotency-Keystring

Required for signed sensitive requests and recommended for all sensitive mutating requests. Replays are scoped to authenticated or explicitly signed contexts.

Request body

OR

Example request

{
  "coin": "xyz:SPCX",
  "asset": "xyz:SPCX"
}

Response

JSON response

oktrue required

Changes

Changed in 1 of the 9 revisions of this API.1