Authentication
Send customer keys with X-API-Key. Public evaluation stays rate-limited; paid keys are account-backed and visible in /api-keys.
Developer docs
Evaluate Signals API quickly, then move to account-backed keys when usage matters.
The API is packaged around structured disruption events, canonical URLs, usage visibility, archive tiers, and beta webhook delivery.
Rate posture
Starter, Growth, and Enterprise packages receive separate throughput, archive, and webhook controls. Usage is metered by account and key.
Schema safety
Current public docs target schema_version 2026-04-22. Clients should store schema_version and ignore unknown fields.
Webhook beta
Webhook delivery is entitlement-gated. Use event_id for dedupe, verify signatures when enabled, and fall back to canonical_url for analyst handoff.
Endpoints
Core routes for evaluation and paid integrations.
| Method | Path | Purpose |
|---|---|---|
| GET | /api/v1/stories | List recent event-first story signals with filters for category and pagination. |
| GET | /api/v1/stories/{story_id} | Fetch a single signal by story/event ID with canonical URL and safe preview fields. |
| GET | /api/v1/categories | Inspect supported categories for filter builders. |
| GET | /api/v1/trending | Evaluate high-engagement or fast-developing signals. |
| GET | /api/v1/stories/{story_id}/engagement | Attach social and downstream engagement context where available. |
Authentication
curl -H "X-API-Key: $ZETTAWIRE_API_KEY" \ "https://api.zettawire.com/api/v1/stories?category=security"
Client guidance
- Persist `schema_version` and `event_id` with each processed signal.
- Use `canonical_url` when routing analysts back to human-readable context.
- Back off on 429 responses and separate beta webhook delivery from polling.
- Do not treat `developing` or `single_source` events as fully confirmed.
Beta access
Request Signals API beta access with source attribution.
We use this form to understand developer demand, integration use cases, and which public pages produce qualified API leads.
Submissions are stored through newsletter attribution today, so the growth dashboard can group leads by page, campaign, and source while we keep API-key issuance entitlement-gated.