Air Raid Alert API (Ukraine, UNOFFICIAL)

(Ukrainian version is available here.)

This API allows you to query air raid alerts in Ukraine in real-time.

Data is taken from

Events are usually delayed for up to 2 seconds.

Only regions are supported at this moment - 24 total plus Kyiv city. Crimea is absent from this list since no information is available. But we all know that Crimea is Ukraine.

Service works in two modes: HTTP and TCP.

You can use our static map:

You can also retrieve history of all alerts as time series dump (see section A2).

Alert Map

Please note that this is not an official service. We are not responsible for any damages that may be done to other parties with our service.

You can use our API for any purpose, even commercially. The only exception is: using our API to perform destructive actions against Ukraine is strictly prohibited. This is considered a felony and will be reported to Security Service of Ukraine.

Our projects

A. HTTP mode

A1. Authentication

You will need a key to use this API.

Please be aware that this API is rate-limited:

If you exceed the above limits you will be throttled with a HTTP 429 response.

A2. Endpoints

GET /api/states

Returns the list of regions with their statuses.

# $ curl -H "X-API-Key: yourApiKey34421337"

  "states": [
      "id": 1,
      "name": "Вінницька область",
      "name_en": "Vinnytsia oblast",
      "alert": false,
      "changed": "2022-04-05T06:12:52+03:00"
      "id": 2,
      "name": "Волинська область",
      "name_en": "Volyn oblast",
      "alert": false,
      "changed": "2022-04-05T06:13:06+03:00"
    # ...
  "last_update": "2022-04-05T06:15:10.333210918+03:00"

You can also append ?short to URL in order to receive only id and alert fields to reduce bandwidth.

GET /api/states/<ID>

Returns status for single region.

# $ curl -H "X-API-Key: yourApiKey34421337"

  "state": {
    "id": 12,
    "name": "Львівська область",
    "name_en": "Lviv oblast",
    "alert": false,
    "changed": "2022-04-05T06:13:12+03:00"
  "last_update": "2022-04-05T06:15:10.333210918+03:00"

GET /api/states/live & GET /api/states/live/<ID>

SSE endpoint which yields alert events in real time.

If you pass ID, you will receive events related to the requested region only.

Client example:

# $ curl -H "X-API-Key: yourApiKey34421337"

event: hello
data: null

event: ping
data: null

event: ping
data: null

event: update
data: {"state":{"id":12,"name":"Львівська область","name_en":"Lviv oblast","alert":false,"changed":"2022-04-05T06:14:56+03:00"},"notification_id":"b7b5cb85-ddc0-11ec-90d3-c8b29b63332d"}

event: ping
data: null

# ...

GET /api/history

Returns history of all alerts.

This endpoint can be called only once per minute.

# $ curl -H "X-API-Key: yourApiKey34421337"

  # ...

B. TCP Mode

If you want to use this API in embedded systems - e.g. Arduino or ESP8266, you might prefer a more lightweight protocol instead of HTTP. This is why we offer a simple TCP interface.

TCP-server is running on on port 1024.

Example project for ESP8266:

B1. Packet structure

All messages from server have the following format:


Every packet to and from server must end with an ASCII line break (\n).

Packet type Description Data
a auth packet, contains authentication result ok, timeout or wrong_api_key
p ping packet, server sends this every 15 seconds Random number in range [0;10000)
s state packet, contains information about air raid alert in specific region Region number and air raid alert value. E.g. during air raid alert activation in Lviv region this will contain 12=1

B2. Communication protocol

  1. Client connects and sends its API key (ASCII encoding) within 3 seconds:


    This is the only packet that client sends to the server.

    You can also request updates for a single region only by appending a comma-separated region number to your key, e. g.:

  2. Server sends auth packet which tells whether authentication was successful.


    If authentication has failed, error code will be provided instead of ok (see previous section).

  3. Server initially sends 1 state packet for each region.

  4. Server periodically sends ping packets (every 15 seconds).

  5. During air raid alert activation or deactivation, server sends state packet.

Sample TCP session (prefix > means serverbound, < means clientbound, # denotes comments):

> yourApiKey34421337     # Client sends API key
< a:ok                   # Authentication successful
< s:1=0                  # Initial data about 25 regions
< s:2=0
< s:3=0
...                      # (20 lines skipped for brevity)
< s:24=0
< s:25=0
< p:1241                 # Ping packet
< p:2508                 # ...
< p:1902
< p:9028
< s:12=1                 # Air raid alert in Lviv region!
< p:3819
< p:9873
< s:12=0                 # Air raid alert in Lviv region has been canceled.
< p:8321                 # Ping packet
< p:3985                 # ...

Use the source, Luke

This thing was made by Andrew Dunai.

Source code for this service can be found here:

But why?

I support and preach the principles of open data and FOSS.

I believe that everyone should be allowed to process any information which is publicly available in any ways they choose, unless they are harming others.

But… Doesn’t ”free” mean ”free of charge”? Isn’t free and ”libre” the same?

“Free” (as in beer) and “free” (as in freedom, also called “libre”) are totally different concepts.

For example, Instagram is free of charge. However it’s not freedom: they force you to use their own application and refuse to provide you full access over your data. In fact, they give you some control but it’s very limited and heavily supervised. This is what “non-free” means in the context of computer technologies.

Don’t become vendor-locked.

Let’s make our world libre.