Skip to main content
GET
Export Events
Export all matching events in the specified format. Returns a streaming file download, not a JSON envelope. The response includes a Content-Disposition: attachment; filename="events.<ext>" header. Clients must write the response body directly to disk or a buffer — do not call .json() on the response.

Query Parameters

Export Formats

CSV Format

Standard comma-separated values with headers. Includes all event fields plus flattened actor information. Use case: Import into Excel, Google Sheets, or data analysis tools Content-Type: text/csv; charset=utf-8 File extension: .csv Example Request:

JSON Format

Array of complete EventDetailResponse objects with full metadata and nested actors. Use case: Programmatic processing, full data fidelity, custom analysis Content-Type: application/json File extension: .json Response Structure:

GeoJSON Format

RFC 7946 compliant GeoJSON FeatureCollection suitable for mapping applications. Use case: Mapping applications, GIS tools, Leaflet, Mapbox, OpenLayers Content-Type: application/geo+json File extension: .geojson Response Structure:
Example Request:

ACLED Format

Compatible with ACLED (Armed Conflict Location & Event Data Project) schema. Only available for conflict category events. Use case: Integration with existing ACLED workflows, research tools expecting ACLED format Content-Type: application/json File extension: .json

ACLED Field Mapping

Additional Non-ACLED Fields:
  • salience_score: Relevance/importance score (0.0-1.0)
  • salience_rationale: Explanation of salience score
  • dedup_key: Deduplication identifier
  • event_date_end: End date for multi-day events
Example Response:
Example Request:

Flat Format

Denormalized JSON with actor positions as explicit columns, suitable for spreadsheet import and tabular analysis. Use case: Spreadsheet import where actor relationships need to be explicit, business intelligence tools Content-Type: application/json File extension: .json

Flat Format Actor Fields

Example Response:
Example Request:

Actor Position Hierarchy

Understanding the actor position fields in ACLED and Flat formats:

Position Types

  1. Principal/Secondary (actor1/actor2): Main actors in the event
  2. Sub-Principal/Sub-Secondary (assoc_actor_1/assoc_actor_2): Internal organizational units
    • Same organization as the main actor
    • Examples: military divisions, regional branches, internal factions
  3. Supporting Principal/Supporting Secondary (supporting_actor_1/supporting_actor_2): External support
    • Different organizations providing assistance
    • Examples: foreign military support, allied groups, coalition partners

Example Scenarios

Military operation with foreign support:
Rebel coalition:

Response Codes

Rate Limits

  • 100 requests per minute per API key
  • 10,000 requests per day per API key
Contact support for higher limits if needed for your use case.

See Also