/acled/regional-updates

POST /api/acled/regional-updates

Price: 20 credits

ACLED's monthly regional overview for Africa, Asia-Pacific, Europe and Central Asia, Latin America and the Caribbean, the Middle East, or the United States and Canada: the key developments by country, authors, countries covered and the month of political violence and demonstration events behind the overview's map

How to use it

Without month and year returns the current edition. Each edition carries the events of the month before its publication month; editions without an event map return an empty events list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• region string required — Region of the overview (one of: "africa", "asia-pacific", "europe-and-central-asia", "latin-america-and-caribbean", "middle-east", "united-states-and-canada"; examples: "africa")
• month string nullable — Month of the edition; with year, picks a past edition (one of: "january", "february", "march", "april", "may", "june", "july", "august", "september", "october", "november", "december"; examples: "june")
• year integer nullable — Year of the edition; with month, picks a past edition (examples: 2026; min: 2019; max: 2100)

Response

• @type string (default: "AcledRegionalUpdate")
• url string required
• region string required (one of: "africa", "asia-pacific", "europe-and-central-asia", "latin-america-and-caribbean", "middle-east", "united-states-and-canada")
• published_date string nullable
• summary string nullable
• authors array (default: [])
  • @type string (default: "AcledAuthor")
  • name string required
  • role string nullable
  • url string nullable
• countries array (default: [])
• regions array (default: [])
• sections array (default: [])
  • @type string (default: "AcledUpdateSection")
  • heading string nullable
  • text string required
• events_count integer (default: 0)
• events array (default: [])
  • @type string (default: "AcledRegionalEvent")
  • id string required
  • event_date string nullable
  • disorder_type string nullable
  • event_type string nullable
  • country string nullable
  • admin1 string nullable
  • latitude number nullable
  • longitude number nullable

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 — ACLED published no overview for this region and month 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.