Authorizations
Hyperliquid uses a custom signing scheme for authentication.
Required for: All /exchange endpoints
Format: Signature generated using private key + nonce + action data
Headers:
- Authorization: Signature
- Content-Type: application/json
Important Notes:
- Use official SDKs to avoid signing errors
- Nonce must be current timestamp in milliseconds
- Address fields must be lowercase
- Order of fields in msgpack serialization matters
Common Pitfalls:
- Not understanding the two signing schemes
- Trailing zeros on numbers
- Case sensitivity on addresses
- Incorrect field ordering