For the complete documentation index, see llms.txt. This page is also available as Markdown.

Combat Sample

Combat hazards cover military strikes and operations against military or state targets. The sample below is a MISSILESTRIKE — a Russian missile and drone strike on the Ukrainian power grid, corroborated across 247 articles.

Combat hazards are frequently the most heavily corroborated records in the feed, and are the most likely to be updated repeatedly as reporting develops. Poll with the since parameter rather than refetching the whole feed. They also linger longest when no end is detected — 168 hours rather than the usual 96 — because active fronts can go quiet for days without being over.

These hazards are returned by the /osint-hazards-query endpoint, which requires a specific role on your credentials.

Sub-types (hazard_sub_type): AIRSTRIKE, MISSILESTRIKE, DRONESTRIKE, BOMBING, ARTILLERY, GROUNDCOMBAT (default), INVASION, NAVAL, IED, AMBUSH

Type-Specific Properties

Incident properties specific to combat:

  • Aggressor — the party conducting the strike or operation

  • Target — the party or asset targeted

  • Infrastructure_Hit — infrastructure reported struck

  • Weapons_Used — weapon systems reported used

Strikes on ports, rail, and energy infrastructure also populate the supply-chain fields. In the sample below, seaport infrastructure in Odesa was struck, so the hazard is returned by supply_chain=true with SupplyChainInfrastructure: PORT and SupplyChainDisruptionType: DAMAGE.

Quantitative counters (n2h.quantitative):

Combat carries the richest counter set of any type — missiles_fired, missiles_intercepted, drones_launched, drones_intercepted, buildings_damaged, buildings_destroyed, plus casualty counts broken down as civilian_deaths / military_deaths and civilian_wounded / military_wounded.

Counters suffixed _cumulative_since and _running_total accumulate across the life of a long-running conflict rather than describing the single strike. Read the unsuffixed keys for the incident itself.

Sample Response

Note: Coordinate arrays have been replaced with [...] for brevity. In actual API responses, these properties contain complete GeoJSON coordinate arrays. The n2h.sources array and the incident.properties and features objects have been truncated with "..." to show only key fields, and article text has been elided. The n2h.extra object is reserved for internal use.

Last updated