DATA FOR YOUR TOOLS
HOSTuvo Data API v1: integrate data with its context
Build views from read-only HOSTuvo results while preserving instrument, source, horizon and freshness.
The API exposes selected analytical results, not exchange execution or private model internals. HTTP success means the request succeeded; it does not make every nested metric current or executable. Display unavailable values and delayed observations explicitly.
Authentication
Send Authorization: Bearer with every request. Keys use the hst_v1_ prefix and can be revoked immediately.
- Up to 3 active keys.
- The full secret is shown once.
- PRO expiry disables access.
Limits and security
v1 allows 60 requests per minute and 10,000 per day.
- 429 when limits are exceeded.
- 401 for missing/invalid keys.
- 403 when entitlement is missing.
v1 endpoints
Markets, snapshots, history, Top 10, Accumulation, PRE-MOVE, context and system status.
- /api/v1/markets
- /api/v1/market/INJUSDC/snapshot
- /api/v1/opportunities/top10
- /api/v1/accumulation/top10
- /api/v1/premove/INJUSDC
What it does not do
No order execution, no exchange keys and no private model internals.
- auto_orders stays OFF.
- No BUY/SELL/ORDER endpoints.
- No infrastructure secrets.
Build a resilient polling loop
Poll the endpoints your view needs and reuse responses across components. Do not repeat a burst immediately after failure. For rate limits, respect a server-provided retry instruction; otherwise use bounded backoff. Stop and explain authentication or entitlement errors instead of repeating an invalid request. A missing field must remain unavailable rather than becoming zero.
- Set timeout and cancellation.
- Avoid duplicate requests after reconnect.
- Display observation time beside cached results.
Keep analytical meaning during export
Retain symbol, reference or execution venue, horizon, observation time and diagnostic status with every PRE-MOVE row. A Top 10 place is a ranking within a scan, not a probability or exchange order. If a spreadsheet joins snapshots from different times, show that mismatch. Compare the same forecast definition when calculating your own summaries.
- Carry provenance into CSV and databases.
- Distinguish null, zero and unavailable.
- Separate simulated from executed outcomes.
Keep API keys out of public pages
Generate a key through the authorised account interface and store it outside public frontend code, screenshots and shared spreadsheets. Route a public dashboard through your own server when it needs a secret. Revoke unused keys and update the consuming service deliberately. Handle lost entitlement as an access state instead of silently replacing the PRO response with invented data.
- Never paste the full key into a support message.
- Use documented read-only endpoints.
- Test errors without financial transactions.
curl https://app.hostuvo.com/api/v1/opportunities/top10 \
-H "Authorization: Bearer hst_v1_YOUR_KEY"Create a key in your account panel. The full secret is shown once; keep it on your server.
Continue learning