DEVELOPER ACCESS // PUBLIC BETA

Build on the watch floor.

Read IntelMap's normalized global signals, 30-day archive, routing observations and current maritime-security incidents. Public reads are free, require no API key and support cross-origin browser requests.

Authentication: None
Access fee: $0
Format: JSON
Base URL: intelmap.watch/api

01 / QUICKSTART

One request. No signup.

TERMINALcurl --compressed "https://intelmap.watch/api/feed/"

BROWSERconst data = await fetch('https://intelmap.watch/api/feed/').then(r => r.json());

Responses include freshness timestamps and standard HTTP cache headers. Cache locally and avoid requesting an endpoint more frequently than its advertised max-age.

02 / ENDPOINTS

Supported public reads.

Download OpenAPI 3.1 →

GET/api/feed/60s cache

Current intelligence feed

The complete active IntelMap snapshot: normalized events, locations, categories, confidence, source health and generation metadata.

Open live response ↗

GET/api/history/60s cache

Historical signals

Query the rolling 30-day archive or retrieve a single signal and its recorded evolution.

hours: 1–87,600; defaults to 168
from / to: ISO date or timestamp
country: Exact country name
category: Signal classification
limit: 1–500
offset: Pagination offset
id: 12-character signal identifier
mode: countries or calendar

Open 24-hour example ↗

GET/api/network/30s cache

Internet routing observations

Cached RIPE RIS sampling with withdrawal bursts, origin changes and investigative caveats. Observations are leads, not confirmed hijacks.

Open live response ↗

GET/api/piracy/300s cache

Maritime-security incidents

A GeoJSON FeatureCollection of current ReCAAP observations plus the latest IMO report reference. This is informational data, not a navigational warning.

Open GeoJSON response ↗

GET/api/popularity/30s cache

Most watched signals

Deduplicated reader-interest rankings for the current 24-hour window.

limit: 1–20; defaults to 8

Open top-ten response ↗

03 / OPERATING POLICY

Free access. Responsible use.

Cache what you read

Honor Cache-Control, use a descriptive User-Agent for server requests and apply backoff after 429 or 5xx responses. Automated bulk mirroring may be restricted to protect the public service.

Preserve provenance

Display IntelMap attribution, retain each event's named source and link users to the original report. API access does not transfer ownership of third-party reporting.

Verify consequential claims

Confidence scores are heuristics. Routing, safety and incident data require independent confirmation and must not be used as an emergency or navigational warning service.

Mixed-source terms

Underlying providers retain their own terms. Live aircraft and vessel-position endpoints are intentionally outside this supported developer contract; obtain data directly from those providers for third-party applications.