# /acled/ukraine/events

`POST /api/acled/ukraine/events`

Price: 350 credits

Political violence events of the war in Ukraine from ACLED's Ukraine Conflict Monitor — battles, shelling, air and drone strikes and violence against civilians in Ukraine and Russia since February 2022, with actors, location, fatalities, drone use and the infrastructure hit

## How to use it

Newest events first. Filters combine with AND; admin1 is the oblast name as ACLED spells it (Donetsk, Kyiv City, Belgorod). Events carry no id of their own.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `date_from` (string, nullable) — Only events on or after this date (YYYY-MM-DD) (examples: "2026-09-01")
- `date_to` (string, nullable) — Only events on or before this date (YYYY-MM-DD) (examples: "2026-09-18")
- `country` (string, nullable) — Only events in this country (one of: "Ukraine", "Russia"; examples: "Russia")
- `admin1` (string, nullable) — Only events in this first-level region (oblast) (examples: "Donetsk"; maxLength: 100)
- `event_type` (string, nullable) — Only events of this type (one of: "Battles", "Explosions/Remote violence", "Violence against civilians", "Riots"; examples: "Battles")
- `sub_event_type` (string, nullable) — Only events of this sub-type (one of: "Air/drone strike", "Shelling/artillery/missile attack", "Armed clash", "Remote explosive/landmine/IED", "Attack", "Non-state actor overtakes territory", "Abduction/forced disappearance", "Government regains territory", "Sexual violence", "Mob violence", "Grenade", "Suicide bomb", "Chemical weapon"; examples: "Air/drone strike")
- `infrastructure` (string, nullable) — Only events that hit this kind of infrastructure (one of: "Residential infrastructure", "Energy infrastructure", "Education infrastructure", "Health infrastructure"; examples: "Energy infrastructure")
- `actor` (string, nullable) — Text contained in the name of an actor or associated actor (examples: "Wagner"; maxLength: 200)
- `is_drone` (boolean, nullable) — Only drone events, or only non-drone events
- `is_civilian_targeting` (boolean, nullable) — Only events targeting civilians, or only events that do not
- `min_fatalities` (integer, nullable) — Only events with at least this many fatalities (examples: 10; min: 0)
- `count` (integer, required) — Max number of events to return (examples: 100; min: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "AcledUkraineEvent")
- `event_date` (string, required)
- `disorder_type` (string, nullable)
- `event_type` (string, nullable)
- `sub_event_type` (string, nullable)
- `actor1` (string, nullable)
- `assoc_actor_1` (string, nullable)
- `actor2` (string, nullable)
- `assoc_actor_2` (string, nullable)
- `country` (string, nullable)
- `admin1` (string, nullable)
- `latitude` (number, nullable)
- `longitude` (number, nullable)
- `fatalities` (integer) (default: 0)
- `is_civilian_targeting` (boolean) (default: false)
- `is_drone` (boolean) (default: false)
- `infrastructure_tags` (array) (default: [])

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.

### 412

The entity was not found, or a precondition failed

What to do: Retrying will not help: either the entity does not exist, or the input points at a different one.

### 429

Too many requests: a rate limit or a usage window is exhausted

What to do: When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.

### 500

Something broke on our side

What to do: Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.

### 529

Rate limit reached, or the endpoint is overloaded

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these headers:

- `X-Error` — Error message text (present only on error)
- `X-Request-ID` — Unique request identifier
- `X-Execution-Time` — Execution time in seconds
- `X-Result-Count` — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
- `X-Total-Available-Results` — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
- `X-Warning` — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
- `X-Retry-After` — Seconds to wait before retrying. Present only on 429.