Developer Reference
Scope Public API — v1
A read-only REST API over the Scope alert database. Pipe congressional trades, insider filings, corroborated signals, and sector heat directly into your own models and dashboards.
Authentication
Every request requires an API key, passed either as the X-API-Key header or an ?api_key= query parameter. Keys are issued on request — contact the Scope team.
# header form (recommended)
curl -H "X-API-Key: scope_your_key_here" \
https://scope-production-1c3a.up.railway.app/api/v1/alerts?days=7
# query-param form
curl ".../api/v1/heat-index?api_key=scope_your_key_here"
All list endpoints return a standard envelope:
{ "data": [ ... ], "total": N, "page": 1, "per_page": 50 }
Endpoints
GET/api/v1/alerts
Paginated alert feed across all rules.
params: severity, rule, ticker, days (1–365, def 7), page, per_page (1–200, def 50)
GET/api/v1/alerts/{id}
A single alert by ID, with full detail and metadata.
GET/api/v1/ticker/{symbol}/signals
All signals for a ticker across every rule.
params: days (def 90), page, per_page
GET/api/v1/member/{bioguide_id}/trades
Disclosed trades for a member of congress.
params: days (def 90), page, per_page
GET/api/v1/heat-index
Current heat score, trend, and dominant rule for every sector.
params: days (1–90, def 30)
GET/api/v1/corroborations
RULE_10 cross-source corroborations — the flagship signal.
params: days (def 30), page, per_page
Example response
{
"data": [
{
"id": 1839,
"rule": "RULE_10",
"ticker": "LMT",
"severity": "CRITICAL",
"headline": "[CORROBORATION] LMT: 3 independent instruments in 14d",
"created_at": "2026-06-08 13:20:11"
}
],
"total": 12, "page": 1, "per_page": 50
}
Errors
401 missing key · 403 invalid key · 404 not found. Rate limits are generous for normal use; abusive traffic may be throttled.
Data is provided for informational purposes only and does not constitute investment advice.