> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.
# spotDeploy | Hyperliquid exchange
> Deploys a new spot token on Hyperliquid. Requires winning the spot pair deployment auction. Chainstack Hyperliquid exchange reference.
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](/docs/hyperliquid-methods) for the full availability breakdown.
This endpoint requires signature authentication. See our comprehensive [Authentication via Signatures guide](/docs/hyperliquid-authentication-guide) for implementation details.
Deploys a new spot token on Hyperliquid. Requires winning the spot pair deployment auction.
## Parameters
### Required parameters
* `action` (object, required) — The action object containing:
* `type` (string) — Must be `"spotDeploy"`
* `config` (object) — Spot token deployment configuration
* `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
```shell cURL theme={"system"}
curl -X POST https://api.hyperliquid.xyz/exchange \
-H "Content-Type: application/json" \
-d '{
"action": {"type": "spotDeploy"},
"nonce": 1234567890123,
"signature": {...}
}'
```
```python Python (hyperliquid-python-sdk) theme={"system"}
import eth_account
from hyperliquid.exchange import Exchange
from hyperliquid.utils import constants
# Public Hyperliquid mainnet — this method is not served by Chainstack
wallet = eth_account.Account.from_key("0xYOUR_PRIVATE_KEY")
exchange = Exchange(wallet, constants.MAINNET_API_URL)
# Step 1 of the spot deploy flow: register the token (registerToken2)
result = exchange.spot_deploy_register_token(
token_name="USDC",
sz_decimals=8,
wei_decimals=8,
max_gas=1000000,
full_name="USD Coin",
)
print(result)
```
```typescript TypeScript (@nktkas/hyperliquid) theme={"system"}
import * as hl from "@nktkas/hyperliquid";
import { privateKeyToAccount } from "viem/accounts";
const wallet = privateKeyToAccount("0xYOUR_PRIVATE_KEY"); // viem or ethers
// Public Hyperliquid mainnet — this method is not served by Chainstack
const transport = new hl.HttpTransport();
const client = new hl.ExchangeClient({ transport, wallet });
// Step 1 of the spot deploy flow: register the token (registerToken2)
const result = await client.spotDeploy({
registerToken2: {
spec: {
name: "USDC",
szDecimals: 8,
weiDecimals: 8,
},
maxGas: 1000000,
fullName: "USD Coin",
},
});
console.log(result);
```
## Use case
* **Spot deploy** — Deploys a new spot token on Hyperliquid. Requires winning the spot pair deployment auction.
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.
## OpenAPI
````yaml openapi/hyperliquid_node_api/hypercore_exchange/exchange_spot_deploy.json post /exchange
openapi: 3.0.0
info:
title: Hyperliquid Exchange API
version: 1.0.0
description: >-
API for trading operations on Hyperliquid exchange. **IMPORTANT**: All
exchange endpoints require EIP-712 signatures for authentication. The
examples shown will not work without proper signing. See the [Hyperliquid
Python SDK](https://github.com/hyperliquid-dex/hyperliquid-python-sdk) for
implementation examples.
servers:
- url: https://api.hyperliquid.xyz
security: []
paths:
/exchange:
post:
tags:
- hyperliquid exchange
summary: Spot deploy
operationId: spotDeploy
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
action:
type: object
properties:
type:
type: string
default: spotDeploy
enum:
- spotDeploy
description: >-
Action type. The action object must contain exactly one
sub-action field.
registerToken2:
type: object
description: >-
Register a new HIP-1 token (one of several possible
sub-actions)
properties:
spec:
type: object
properties:
name:
type: string
description: Token ticker symbol
szDecimals:
type: integer
description: Size decimal places
weiDecimals:
type: integer
description: Wei decimal places
maxGas:
type: integer
description: Maximum gas for deployment
fullName:
type: string
description: Full display name of the token
required:
- type
nonce:
type: integer
description: Current timestamp in milliseconds
signature:
type: object
description: EIP-712 signature of the action with r, s, v components
properties:
r:
type: string
description: ECDSA signature r component (hex string)
example: >-
0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
s:
type: string
description: ECDSA signature s component (hex string)
example: >-
0xfedcba0987654321fedcba0987654321fedcba0987654321fedcba0987654321
v:
type: integer
description: ECDSA recovery id (27 or 28)
example: 27
required:
- r
- s
- v
vaultAddress:
type: string
description: >-
Address when trading on behalf of a vault or subaccount
(optional)
nullable: true
required:
- action
- nonce
- signature
example:
action:
type: spotDeploy
registerToken2:
spec:
name: MYTOKEN
szDecimals: 8
weiDecimals: 8
maxGas: 100000
fullName: My Custom Token
nonce: 1705234567890
signature:
r: >-
0x0000000000000000000000000000000000000000000000000000000000000000
s: >-
0x0000000000000000000000000000000000000000000000000000000000000000
v: 27
vaultAddress: null
responses:
'200':
description: Action result
content:
application/json:
schema:
type: object
properties:
status:
type: string
description: Request status
response:
type: object
description: Action response data
````