---
title: Trading Accounts
description: Read and rename venue-scoped managed trading accounts.
---

Trading accounts are existing managed wallets owned by your authenticated Superior account and scoped to one venue: `hyperliquid`, `polymarket`, or `lighter`.

Use the literal venue in every route:

```http
GET  /account/{venue}
GET  /account/{venue}/{id}
PATCH /account/{venue}/{id}
GET  /account/{venue}/{id}/wallet
```

`GET /account/{venue}` returns `{ "accounts": [...] }`, ordered by `account_index`. Detail and rename return `{ "account": {...} }`. Each account has common fields plus a venue-discriminated `details` object; private provider IDs, signing material, and venue credentials are never returned. Unified API does not create trading accounts.

## Read, rename, and inspect the wallet

Pass both the venue and account ID. A foreign account or an ID under the wrong venue returns the same `404 trading_account_not_found` response.

```bash
curl https://api.superior.trade/account/hyperliquid/{id} \
  -H "x-api-key: $SUPERIOR_TRADE_API_KEY"

curl -X PATCH https://api.superior.trade/account/hyperliquid/{id} \
  -H "x-api-key: $SUPERIOR_TRADE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"label":"Primary Hyperliquid"}'
```

`GET /account/{venue}/{id}/wallet` returns the same complete managed-wallet overview schema documented in [Wallet Overview](/wallet/overview), selected for that owned trading account.

There is no delete, disable, archive, transfer, withdrawal, or claim-back action under `/account/{venue}`.