Market data. Ready to use.
Try a request, copy the code, or hand a clear brief to your AI assistant.
Latest public signals
Public · no key neededThe latest published trading signals across tracked markets.
No request sent yet.
Live risk updates
Subscribers connect to /ws/risk?pair=ETH_USDT. Omit the pair for the market grid. A risk_update message arrives every 30 seconds; hourly data may be unchanged.
Connection & payload
Use a same-origin browser session cookie or a Bearer header from your server-side WebSocket client. No keys in URLs. Close when idle and reconnect with backoff.
{"event":"risk_update",
"snapshot":{...}, "history":[...],
"refresh_seconds":30}Grid messages contain cards instead. Risk computation is shared and demand-driven; active email alerts can also trigger it.
Know what you’re reading
Risk outlooks are price-history estimates, not the trading algorithm’s signals. Use the signals endpoints for trading signals.
Errors & safe usage
Check HTTP status before parsing results. Handle 401/402/403 as access errors, 404 as unavailable data, and 429 with backoff. Treat stale or missing data as unavailable—not a zero price. Respect refresh_seconds and keep keys server-side.
Give your AI a head start
A copyable integration brief. No secrets included.
Custom forecasts & other streams
POST /api/forecast/line accepts series, prediction_length, and interval. It consumes credits and is deliberately excluded from this read-only tester. Check your available credits and current cost before submitting.
curl -X POST 'https://bitbank.nz/api/forecast/line' \
-H "Authorization: Bearer $BITBANK_API_KEY" \
-H 'Content-Type: application/json' \
-d '{"series":[1,1.2,1.15,1.3,1.4,1.35,1.5,1.6,1.55,1.7,1.75,1.8],"prediction_length":7,"interval":"HOUR_1"}'The existing trading stream remains at /ws using subscribe_live. The dedicated risk stream is separate.