01
Claim an API token.
Start with public evaluation, then move into account-backed keys when integration usage matters.
$ zw auth login --workspace risk-desk
API live
06:42:18Zsignals ingest steady across global edgePROD06:41:55Zedge-jfk p50 latency 38ms, p99 112msJFK06:41:32Zschema 2026-04-22 available for evaluationREL06:41:08Zwebhook beta routing active for Growth accountsBETA06:40:50Zsource confidence rollups refreshedQC06:42:18Zsignals ingest steady across global edgePROD06:41:55Zedge-jfk p50 latency 38ms, p99 112msJFK06:41:32Zschema 2026-04-22 available for evaluationREL06:41:08Zwebhook beta routing active for Growth accountsBETA06:40:50Zsource confidence rollups refreshedQC
Signals API - v2.4
Wire-grade events, piped straight into your stack.
Structured ZettaWire event signals behind customer keys, usage posture, archive packaging, and a webhook rollout path. Public access stays lightweight while paid access becomes an operational surface for products, automations, and partner delivery.
Primary use
Operational APIs
Delivery
Keys + webhooks
Archive
24h to 24mo
Schema
2026-04-22
stream-events.ts
# Query recent maritime disruption signals.
curl "https://api.zettawire.com/api/v1/stories?category=security&min_score=0.7" \
-H "X-API-Key: $ZETTAWIRE_API_KEY"
-H "Accept: application/json"
// HTTP/2 200 OK
{
"event_id": "evt_20260422_red_sea_18431",
"headline": "Port disruption near Suez corridor raises shipping risk",
"category": "security",
"score": 8.4,
"source_confidence": "multi_source",
"geo": { "region": "Red Sea", "lat": 30.04 }
}ServiceAll systems nominal
RegionsJFK / LHR / NRT / FRA
Last incident11d ago - resolved
Build2.4.1 - schema stable
From key to first event in four minutes.
QuickstartEst. 4 min
02
Pick a signal feed.
Query structured story events by category, geography, score, archive tier, or publication window.
$ GET /api/v1/stories?category=security
03
Filter at the edge.
Keep downstream systems clean with confidence, topic, category, and canonical story filters.
$ --min_score 0.7 --category maritime
04
Ship to production.
Growth and Enterprise teams graduate into controlled webhook delivery and longer archive access.
$ webhook: signal.published
Endpoints.
Base: api.zettawire.com/apiOpenAPI docs ->
Method
Path
Description
Tier
GET
/api/v1/stories
Paginated event-first story signals with category and pagination filters.
Public
GET
/api/v1/stories/{story_id}
Canonical signal record with geography, confidence, and workflow metadata.
Public
GET
/api/v1/categories
Supported category taxonomy for product filters and analyst routing.
Public
GET
/api/v1/trending
Fast-developing or high-engagement signals for monitoring surfaces.
Starter
GET
/api/v1/stories/{story_id}/engagement
Social and downstream engagement context attached to an event.
Growth
GET
/api/v1/briefings
Briefing linkage for teams moving between API objects and desk workflows.
Growth
POST
/api/v1/webhooks
Private-beta webhook endpoint registration and delivery controls.
Beta
The data model.
3 primary objectsVersioned schema
Object
Signal
- event_idstring *
- story_idstring *
- headlinestring *
- categoryenum *
- scorenumber
- source_confidenceenum
- confirmation_statusenum
- canonical_urlurl
- geoobject
- published_atiso-8601
Object
Source
- idstring *
- namestring *
- platformenum
- regionenum
- trust_score0.0-1.0
- latency_p50ms
- latency_p99ms
- verified_atiso-8601
- tagsstring[]
Object
Delivery
- delivery_idstring *
- eventenum *
- webhook_urlurl
- archive_tierenum
- delivery_stateenum
- attemptinteger
- signaturestring
- sent_atiso-8601
- dedupe_keyevent_id
Built by, built for.
Who uses Signals
Risk and intelligence
Brief the desk before the desk reads the news.
Country and sector teams pipe geofenced feeds into internal briefs while keeping canonical ZettaWire context attached.
"Archive depth and source confidence matter more than another generic article feed."Sovereign risk desk
Operations and logistics
Route around disruption while the event is still developing.
Ports, corridors, suppliers, and watchlists can become structured alert inputs instead of manual search jobs.
"The signal payload gives product teams the data shape our operators already use."Supply chain team
Newsrooms and research
Cite the source, the story, and the revision path.
Each event keeps a stable ID, canonical URL, confidence posture, and metadata that can survive CMS and archive workflows.
"We need structured context without losing the human-readable story behind it."Research editor
Plans.
Evaluation to productionCompare packaging ->
Public access
Evaluation
60 requests / hour
24-hour rolling archive
24-hour rolling archive
- Public evaluation surface
- Story and category routes
- No customer keys
- No webhook delivery
Recommended
Signals Starter
Paid
1,000 requests / hour
30-day event archive
30-day event archive
- 2 customer keys
- Usage visibility
- Analyst tooling fit
- Internal automation baseline
Signals Growth
Private beta
5,000 requests / hour
12-month archive
12-month archive
- 5 customer keys
- Webhook beta access
- Production routing
- Longer replay depth
Enterprise
Custom
25,000 requests / hour
24-month archive
24-month archive
- Managed rollout
- Tailored routing
- Partner packaging
- Support-led controls
SDKs and tooling.
Official clientsExamples ->
TypeScript
@zettawire/sdk
npm install ->
Python
zettawire
pip install ->
Go
zw-go
go get ->
Rust
zettawire
cargo add ->
Ruby
zettawire
gem install ->
CLI
zw
brew install ->
Delivery pipeline
Stop scraping. Start subscribing.
Bring the same event layer behind the public ZettaWire product into your internal tools, alerts, market-risk dashboards, and partner applications.
Schematic - ingest -> dedupe -> score -> publish
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.