News distribution API
Consume the canonical News Network feed and its correction, dispute, expiry, retraction, and removal stream. Partner access uses the platform API-key quota and scope model.
Endpoints and scopes
| Endpoint | Scope | Purpose |
|---|---|---|
GET /v1/public/news | news:read | Cursor-paginated story feed. |
GET /v1/public/news/events | news:events | Ordered lifecycle event stream. |
GET /v1/public/news/usage | news:events | Account and key usage report for reconciliation. |
Signed response
Feed and event responses include x-charting-timestamp, x-charting-key-id, and x-charting-signature. Verify the exact response bytes before parsing JSON and reject stale timestamps.
payload = raw_response_body
signed = timestamp + "." + payload
expected = HMAC_SHA256(api_key, signed)
constant_time_compare(expected, signature_v1)curl -i "https://candlescript.io/api/v1/public/news?symbol=NASDAQ:AAPL&limit=25" \
-H "Authorization: Bearer $CHARTING_API_KEY"Corrections and retractions
Poll the compound cursor event stream or subscribe a platform webhook endpoint to news.story.corrected, news.story.disputed, news.story.expired, news.story.retracted, and news.story.removed. Webhooks use the endpoint-specific signing secret and retry/dead-letter policy described in the webhook guide.
Commercial reporting
Distribution usage records request count, returned items, response bytes, endpoint, API key, account, and timestamp. It is intentionally separate from the enforcement counter so quota resets do not erase invoice and reconciliation evidence.