API Reference
Authentication
Read endpoints are open. Writes are authenticated by signature, not by an API key.
There are no API keys
Vordium issues no API keys or secrets. Every state-changing request carries an EIP-712 signature that the chain verifies. Authority comes from the key that signed, so there is no credential to leak, rotate or rate-limit per-tenant.
| Surface | Auth |
|---|---|
Market data (/oracle, /orderbook, /fills, /funding) | None — public |
Account reads (/positions/{addr}, /balance/{addr}) | None — public, address-scoped |
Trading (/order/place, /order/cancel) | EIP-712 signature from an active session key |
| Withdrawals | EIP-712 signature from the owner key |
| Privileged operations | 2-of-3 owner multisig — see Security |
Signing a request
The chain rebuilds the digest from the request body, so the signed values and the posted values must match exactly.
from vordium.caps import place_order_digest
from vordium.dex import Vordex, BUY, LIMIT
vx = Vordex()
res = vx.place_order(
session_key=SESSION_KEY, # signs
owner=OWNER_ADDRESS, # recovered by the chain
pair_id=1, side=BUY, size=0.1, price=2400.0,
leverage=5, order_type=LIMIT,
)Session keys vs the owner key
A session key can trade. It can never withdraw funds or change caps — those are owner-only and enforced natively in consensus.
Never send a private key
No endpoint accepts a private key. Sign locally and send the signature. Anything asking for a key is not Vordium.
See Session Keys for lifetime and scope.