ACLED API
by Armed Conflict Location & Event Data
ACLED API for geocoded political violence and protest events worldwide, with actors and fatalities.
- Category
- Public & Market Data
- Type
- International organisation
- Interface
- REST API
- Built with
- Connect Any API
- Credentials
- OAuth 2.0
- Docs
- ACLED API docs
02Data
What you can sync.
- Conflict events
- Actors
- Fatalities
- Locations
Join ACLED API conflict events with your own figures, so plans and reports carry the market context they need.
Need more? Name any other ACLED API data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- OAuth 2.0 (client ID, client secret, refresh token)
ACLED API uses OAuth 2.0 (client ID, client secret, refresh token). You add the credentials once, when the AI asks for them, and it tells you where to create them in Armed Conflict Location & Event Data if you need help.
04How it works
How it works in DataMind.
-
Pick ACLED API.
Open Lake, pick ACLED API in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the ACLED API docs.
-
Answer a few questions.
The AI reads the ACLED API documentation, then asks which credentials you will use, which data to sync (for example conflict events and actors), whether you want a one-time load or a recurring sync, and which accounts or filters apply.
-
Your data lands in Lake.
It builds the connector, tests it and shows you sample rows. Then ACLED API data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.