Latest News Subscribe

Hedgwatch API
Programmatic access to market briefs, movers, and published research snippets — built for dashboards, bots, and reporting.
Base URL
https://<api.united-river.com>/api/v1
Mode: Read-only Format: JSON (optional HTML snippet) Auth: X-API-Key Use: Dashboards • Alerts • Bots
Hedgwatch publishes informational content only. No execution, no custody. If you need scoped keys (sandbox-only, per-endpoint limits, IP allowlist), request access and we’ll provision it.
Quickstart
Pull today’s brief (same content you show on your market pages).
copy • paste
curl -s -H "X-API-Key: <YOUR_KEY>" \
  "https://<api.united-river.com>/api/v1/briefs/us?format=json"
Tip: if you want to embed the exact rendered markup you use in your Razor pages, call format=html.
Auth & conventions
Simple, audit-friendly, dashboard-friendly.
operational
Timezone: UTC timestamps Caching: ETag / Cache-Control Errors: JSON + status code
GET /api/v1/briefs/us?format=json HTTP/1.1
Host: <api.united-river.com>
X-API-Key: <YOUR_KEY>
Accept: application/json
Typical responses include asOf, market, and items[] so you can store, replay, and audit outputs.
Core endpoints
Designed around your Hedgwatch pages: briefs, movers, categories, and symbols.
v1
Method Endpoint Description
GET /api/v1/briefs/{market}?format=json|html Market brief feed (US / europe / asia / world / crypto / etf / fx).
GET /api/v1/movers/{market}?session=premarket|regular Top movers & leaders/laggards (for “Top Movers” tab/cards).
GET /api/v1/categories Available categories (title, description, key) for navigation.
GET /api/v1/articles?cat=technology&limit=50 Published articles list (for “News” pages, RSS generation, or bots).
GET /api/v1/articles/{id} Single article (content + metadata + source URL).
GET /api/v1/symbols/search?q=AAPL Search symbols (canonical ticker, name, exchange, aliases).
POST /api/v1/watchlist/brief Batch brief for a list of symbols (JSON body) for newsletters/portals.
If you don’t have all endpoints yet, keep the page as-is and wire them up incrementally — start with /briefs/{market}.
Sample response
Simple, predictable shape for clients.
JSON
{
  "market": "us",
  "asOf": "2026-01-07T01:15:00Z",
  "timezoneLabel": "New York (ET)",
  "items": [
    {
      "type": "top_news",
      "title": "AAPL (Apple Inc.)",
      "summary": "Reported growth in sales; positive momentum despite tariff concerns.",
      "tags": ["technology"],
      "sourceUrl": "https://example.com/source",
      "symbols": ["AAPL"]
    }
  ]
}
If you return format=html, the payload can be { asOf, html } so you can embed a sanitized block directly.
Operational notes
What teams usually care about.
SRE-friendly
  • Rate limits: per-key quotas; 429 with retry guidance
  • Stability: versioned routes (/api/v1)
  • Audit metadata: asOf timestamps + request context
  • Safety: decision-support only; no trading / no custody