Public API for monitoring air threats over Ukraine. Data is updated in real time.
https://mapa.ua/api/v1 — all responses are JSON. No authentication is required.
All API methods are open and unrestricted for personal use. The API is also available without restrictions to projects such as Gods Eye View and similar open-data/OSINT projects.
If you are interested in commercial use, or in public use on a large-scale platform, you can request your own API key — usually free, with paid plans for high-volume commercial use. Likewise, if Cloudflare protection gets in the way of your requests, write to us and we will issue you a separate free API key so you can send as many requests as you need without obstacles.
Contact: [email protected] · Telegram: @live_mapa_ua
GET /api/v1/current
Returns the active attack and every object in the air right now.
▶ Try it{
"attack": { "id": 42, "started_at": 1710288000, "status": "active", ... },
"objects": [
{
"id": 1, "kind": "drone_piston", "amount": 1,
"title": "Shahed на Київ", "status": "active",
"lat": 49.12, "lon": 31.45, "heading": 340,
"from_zone": "chauda", "to_city": "kyiv",
"speed_kmh": 165, "trail": [[34.1,45.0,1710288000], ...],
"subkind": "drone_piston",
"predicted_lat": 49.15, "predicted_lon": 31.44
}, ...
],
"raw_count": 15,
"ts": 1710291600
}
GET /api/v1/attacks
List of attacks. Without parameters — the latest 60 attacks (by started_at, newest first).
| Parameter | Type | Description |
|---|---|---|
date | string | Date YYYY-MM-DD (attacks overlapping that day) or nowoptional |
limit | integer | Count, 1–500 (default 60). Ignored when date is setoptional |
nocache | string | 1 — bypass the cacheoptional |
{
"attacks": [
{
"id": 42,
"started_at": 1710288000,
"ended_at": 1710331200,
"status": "ended",
"title": "2025-03-12-20_2025-03-13-08",
"total_objects": 45,
"total_drones": 126,
"total_missiles": 1,
"total_bombs": 0,
"official_drones": 126,
"official_missiles": 1,
"official_bombs": 0,
"official_launched_total": 127,
"official_shot_total": 121
}, ...
]
}
GET /api/v1/objects
All objects (drones, missiles, bombs) of a given attack, with their trails.
| Parameter | Type | Description |
|---|---|---|
attack_id | integer | Attack ID (required) |
{
"objects": [ ... ], // array of objects (same format as /current)
"raw_count": 45 // number of unique groups (before unit expansion)
}
GET /api/v1/attack_replay
Everything needed to replay an attack on a timeline.
| Parameter | Type | Description |
|---|---|---|
attack_id | integer | Attack ID |
{
"attack": { ... },
"objects": [ ... ], // with trail arrays for animation
"raw_count": 45
}
GET /api/v1/trails
Detailed route of a single object.
| Parameter | Type | Description |
|---|---|---|
object_id | integer | Object ID |
{
"trail": [[30.52, 45.10, 1710288000, 340], ...]
// [lon, lat, unix_timestamp, heading_degrees]
}
GET /api/v1/calendar
Number of source messages per day (for picking a date).
▶ Try it{
"days": [
{ "d": "2025-03-13", "c": 847 },
{ "d": "2025-03-12", "c": 623 },
...
]
}
GET /api/v1/countries
Number of russian drones and missiles that entered the airspace of EU countries, Moldova and Norway within a time window. Key — ISO 3166-1 alpha-2 country code, value — estimated number of objects. The response always contains every monitored country (29), including those with zero.
▶ Try it| Parameter | Type | Description |
|---|---|---|
date | YYYY-MM-DD | The attack of that day — the same one the player opens via #replay=DATE: the last finished attack that ended on that day (Kyiv time); today with an active attack — the active one; with no attacks — the Kyiv calendar day optional |
attack_id | integer | Window of a specific attack (from /api/v1/attacks) optional |
from, to | unix, s | Arbitrary window, at most 72 h optional |
hours | integer | Last N hours, 1–72 (default 12) optional |
at | unix, s | State "as of": how many objects had already been over the country by that time (last step with ts ≤ at) optional |
detail | 0 | 1 | 1 — extended response: window bounds, time steps, sources optional |
Window selection priority: attack_id → date → from/to → hours.
GET /api/v1/countries?date=2026-09-24
{ "AT": 0, "BE": 0, "BG": 0, … "MD": 1, … "PL": 0, "RO": 1, … "SK": 0 }
With detail=1:
{
"counts": { "MD": 1, "RO": 1, … },
"window": { "mode": "attack", "attack_id": 649, "date": "2026-09-24", "from": 1790139687, "to": 1790226515 },
"steps": [ { "ts": 1790216741, "cc": "MD", "n": 1 }, { "ts": 1790220536, "cc": "RO", "n": 1 } ],
"events": [ { "ts": 1790216741, "cc": "MD", "n": 1, "kind": "drone", "how": "airspace", "src": "monitorwarr/40784" } ]
}
window.from/window.to are exactly the bounds of the player
slider (the attack's started_at…ended_at). The slider is non-linear, so sync by time, not
by position: the value for a country at moment t is the last step in steps with ts ≤ t
(the at parameter is computed the same way).steps are monotonic within the window: a country's count only grows.ts = attack end
(the slider reaches it), while events keep the real publication time. Aftermath about an already known
live incursion does not add a new drone.events — source messages: src = <channel>/<message id> (t.me/<channel>/<id>); kind — drone | missile; aftermath: true — debris, consequences or statements about an already known case.date means one player attack. In /api/v1/attacks?date= the same parameter returns all attacks overlapping that day.How it is counted. Deterministically, without AI: every message from verified channels is tagged as soon as it arrives, and a country is counted only on an unambiguous phrase within one sentence ("violated the airspace of Moldova", "on the territory of Romania", "over Poland", "crossed the border with Romania", "debris found in Moldova"). Proximity ("near the border", "towards", "heading for") does not count; neither do hypotheticals, negations, retrospectives or reactions ("closed the sky", "scrambled jets"). For Ukraine's neighbours (MD, RO, PL, HU, SK) a drone that arrived via Ukraine is considered russian; for other countries the message must explicitly attribute it to russia. Different channels describe the same drones, so within an episode the maximum is taken, across episodes — the sum.
GET /api/v1/flights
Current civil flights in the area (AirLabs Flight Data API).
| Parameter | Type | Description |
|---|---|---|
scope | string | global — worldwide flights optional |
radius | integer | ADS-B fetch radius around the area, kmoptional |
GET /api/v1/geo/cities
City codes (the objects' to_city field) → display names in Ukrainian and English.
{
"cities": {
"kyiv": { "ua": "Київ", "en": "Kyiv" },
"odesa": { "ua": "Одеса", "en": "Odesa" },
...
},
"ts": 1710291600
}
GET /api/v1/nearby
Active threats within a radius of a given point (based on the current /current snapshot). Per-user, not cached.
| Parameter | Type | Description |
|---|---|---|
lat | float | Latitude (required) |
lon | float | Longitude (required) |
radius_km | integer | Radius, 10–1000 km (default 150)optional |
{
"threats": [
{ "id": "12_u0", "kind": "drone_piston", "subkind": "drone_piston",
"status": "active", "amount": 1, "heading": 320,
"lat": 50.10, "lon": 30.90, "distance_km": 41.3 }, ...
],
"count": 3,
"radius": 150,
"ts": 1710291600
}
Push notifications about threats within a given radius. Delivery is handled by notify.js.
GET /api/v1/push/vapid
Public VAPID key for the browser subscription.
{ "publicKey": "BPx…base64url" }
POST /api/v1/push/subscribe
Store the browser subscription together with the coordinates and alert radius.
// request body (JSON)
{
"subscription": { "endpoint": "…", "keys": { "p256dh": "…", "auth": "…" } },
"lat": 50.45, "lon": 30.52,
"radius_km": 150 // 10–1000, default 150
}
// → { "ok": true, "subscriptions": 1234 }
POST /api/v1/push/update
Update the coordinates/radius of an existing subscription.
{ "endpoint": "…", "lat": 50.45, "lon": 30.52, "radius_km": 200 } // → { "ok": true }
POST /api/v1/push/unsubscribe
{ "endpoint": "…" } // → { "ok": true }
GET /api/v1/recruit/regions
Regions for the "become an information source" block (with a marker counter).
▶ Try it{
"regions": [ { "name": "Одещина", "lat": 46.40, "lon": 30.70, "marker_count": 12 }, ... ],
"count": 8,
"ts": 1710291600
}
POST /api/v1/recruit/click
Record a click on a region / CTA (analytics).
{ "region": "Одещина", "cta_clicked": true } // → { "ok": true }
kind is the main target class. Counters (UAVs / missiles / glide bombs) are computed by it and the official
Air Force reports are reconciled against it.
| Kind | Description | Speed |
|---|---|---|
drone_piston | Shahed-136, Geran, Gerbera, Parodiya, Italmas, Harpy, Lancet, reconnaissance UAVs (Zala, SuperCam, Merlin) | ~165 km/h |
drone_jet | Shahed-238, jet-powered UAVs, S8000 "Banderol" | ~450 km/h |
drone_fpv | FPV drones, "Molniya" — frontline strip, up to ~50 km | ~120 km/h |
missile_cruise | Kalibr, Kh-101, Kh-55, Kh-59, Kh-69, Oniks/P-800 | ~800 km/h |
missile_ballistic | Iskander-M, Kinzhal, KN-23, Zircon | ~7500 km/h |
bomb | KAB, UMPK, UMPB D-30SN, FAB | ~750 km/h |
subkind refines the type within a kind and determines the colour/icon/name on the map. The field
is always present: if the subtype is not recognised it equals kind. For clients: the list of subtypes
may grow — handle unknown values by falling back to kind, not by failing.
| Subkind | Kind | Description | Speed |
|---|---|---|---|
banderol | drone_jet | S8000 "Banderol" — jet-powered loitering munition (a hybrid of a kamikaze drone and a small cruise missile), range up to 500 km. Channels call it a "cruise missile", a "(drone)" or a "loitering munition" — we map every spelling to one type. Official reports count it together with UAVs, hence kind = drone_jet | ~560 km/h |
decoy | drone_piston | Decoy UAV: Gerbera, Parodiya, Italmas, decoy drones | ~165 km/h |
kalibr | missile_cruise | 3M14 "Kalibr" | ~800 km/h |
x101 | missile_cruise | Kh-101 / Kh-55 / Kh-555 | ~800 km/h |
x59 | missile_cruise | Kh-59 / Kh-69 | ~800 km/h |
ballistic | missile_ballistic | Iskander-M, Kinzhal, KN-23, Zircon | ~7500 km/h |
| Status | Description |
|---|---|
active | Object is in the air |
eliminated | Shot down by air defence / mobile fire groups / F-16 |
hit_target | Hit its target |
lost | Disappeared from radar (electronic warfare / decoy) |
| Zone | Description |
|---|---|
chauda | Cape Chauda, Crimea |
crimea | Crimea (general) |
sevastopol | Sevastopol, Crimea |
gvardiiske | Hvardiiske, Crimea |
black_sea_w | Black Sea (west) |
black_sea_e | Black Sea (east) |
novorossiysk | Novorossiysk, russia |
primorsk | Primorsko-Akhtarsk, russia |
eysk | Yeysk, russia |
rostov | Rostov-on-Don, russia |
millerovo | Millerovo, russia |
morozovsk | Morozovsk, russia (glide bombs / aviation) |
kursk | Kursk, russia |
belgorod | Belgorod, russia |
bryansk | Bryansk, russia |
orel | Orel, russia |
shaykivka | Shaykivka, russia (strategic aviation) |
baltimor | Baltimor / Voronezh, russia |
buturlinovka | Buturlinovka, russia |
engels | Engels, russia (strategic aviation) |
caspian | Caspian Sea (cruise missile launches by strategic aviation) |
mozyr | Entry from the north across the Belarus border (Mozyr area) |
tot_donbas | Temporarily occupied Donbas |
tot_zap | Temporarily occupied Zaporizhzhia region |
unknown | Direction not determined |
Array of points: [[lon, lat, unix_ts], ...]
Sorted chronologically. The first point is the launch site, the last one — the current/final position.