/ucdp/fatalities

POST /api/ucdp/fatalities

Price: 65 credits

Fatalities from organised violence since 1989, totalled per year, country, conflict or dyad and split by type of violence, for any combination of country, conflict, dyad, actor, type of violence and year range

How to use it

Totals are UCDP best estimates over georeferenced events. Rows grouped by year come newest first; rows grouped by country, conflict or dyad come deadliest first. An empty list means no recorded event matches.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• group_by string required — One row per year, country, conflict or dyad (one of: "year", "country", "conflict", "dyad"; examples: "year")
• country string nullable — Only events in this UCDP country (examples: "530"; maxLength: 200)
• conflict string nullable — Only events of this UCDP conflict (examples: "16069"; maxLength: 200)
• dyad string nullable — Only events of this UCDP dyad (examples: "17147"; maxLength: 200)
• actor string nullable — Only events where this UCDP actor is a side (examples: "8118"; maxLength: 200)
• violence_type string nullable — Only this type of violence (one of: "state_based", "non_state", "one_sided"; examples: "one_sided")
• year_from integer nullable — First year to include (examples: 2020; min: 1989; max: 2100)
• year_to integer nullable — Last year to include (examples: 2025; min: 1989; max: 2100)
• count integer required — Max number of rows to return (examples: 50; min: 1)

Response

• @type string (default: "UcdpFatalityTotal")
• year integer nullable
• country_id string nullable
• conflict_id string nullable
• dyad_id string nullable
• fatalities integer required
• state_based_fatalities integer required
• non_state_fatalities integer required
• one_sided_fatalities integer required
• events_count integer required
• first_event_year integer required
• last_event_year integer required

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit 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 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 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 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 Wait at least 30 seconds, then retry.

Response 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.