Programmatic Access
Bots and integrations should use an official SDK. The six official SDKs (JS, Python, Rust, C++, Java, Go) handle login (API key id + secret + passphrase), HPKE session or one-shot setup, and order encryption. REST and SSE remain available for auth, account, and stats when you are not building a full trading client.
You still sign up in the app and create API credentials there before any of this works.
SDKs
Clone a language examples repo, add your API key, secret, and passphrase, and run the samples. Each repo vendors the SDK so you do not need a private package registry.
SDK environment presets provide the configured host (the default) and the configured host. See Base URLs.
REST and SSE
| Interface | Protocol | Use |
|---|---|---|
| REST | HTTPS | Auth, account, instruments, /tiers/status, /tiers/config, and /stats/platform; trading via bearer + one-shot HPKE (GodarkRestClient) |
| SSE | HTTPS | Live stats and notifications |
| WebSocket | WSS /ws/v1 | Preferred long-lived trading path (GodarkClient) |
Do not build a raw trading client unless you have a reason to. See Authentication and Encryption & Transport.
Machine tokens have exactly one effective scope: trade or read. Use trade for mutations and either scope for authenticated reads. The authenticated Solana account is carried in JWT sub.
There is no public settlement-status REST endpoint. Track order and position state through the authenticated WebSocket channels and documented snapshots.