How Testnet Works
Every REST endpoint in the Provider API has a testnet variant. Simply prefix the path with/testnet/:
| Environment | URL Pattern |
|---|---|
| Mainnet | https://api.perps.studio/v1/perps/:provider/markets |
| Testnet | https://api.perps.studio/v1/testnet/perps/:provider/markets |
Provider Testnet Support
| Provider | Testnet Available | Testnet Network |
|---|---|---|
| Hyperliquid | Yes | Hyperliquid Testnet L1 |
| Aster DEX | Yes | Aster Testnet |
| Polymarket | No | N/A |
Getting Testnet Tokens
Hyperliquid Testnet
- Go to app.hyperliquid-testnet.xyz
- Connect your wallet
- Use the built-in faucet to get testnet USDC
Aster Testnet
- Go to testnet.aster.finance
- Connect your wallet
- Claim testnet tokens from the faucet
Testnet Differences
Testnet markets may differ from mainnet. Some assets may be unavailable, and liquidity will be significantly lower. Order execution may behave differently due to low volume.
- Fewer markets — testnets typically list a subset of mainnet markets
- Low liquidity — orderbooks are thin; large orders will have significant slippage
- Intermittent availability — testnets may experience downtime or resets
- Different asset IDs — internal identifiers (e.g., Hyperliquid asset indices) differ between mainnet and testnet
Recommended Workflow
Develop on Testnet
Build and iterate using testnet endpoints. Verify market data fetching, order placement, and position management.
Validate Order Flow
Place test orders, verify fills, check positions, and cancel orders. Ensure your error handling covers all cases.