Skip to main content

Data Models

This page documents the complete data structures returned by the Corpus Product API.

EventResponse

The standard event object returned by list endpoints.

Fields

Geo Precision Levels

The geoPrecision field follows ACLED convention for indicating the precision of location coordinates.

Salience Score

The salienceScore field is a confidence score indicating how reliably the event has been verified. Scores below 0.75 are not included in the dataset.

Example JSON

EventDetailResponse

Extended event object with category-specific data. Includes all fields from EventResponse plus:

Category-Specific Data

The categorySpecificData field contains metadata fields defined by the event’s category. See each category’s taxonomy page for the specific fields available. Example for Conflict event:

ActorResponse

The standard actor object returned by list endpoints.

Fields

Note: The actor type/category is not included in the response object. To filter actors by type, use the actor_type query parameter when calling /v1/actors, and use the /v1/metadata/actor-types endpoint to discover available types.

Example JSON

ActorDetailResponse

Extended actor object with relationship breakdowns. Includes all fields from ActorResponse plus:

PaginatedEventsResponse

Wrapper for paginated event listings.

Example JSON

PaginatedActorsResponse

Same structure as PaginatedEventsResponse but with items as ActorResponse[].

CountryAggregation

Country with event count.

RegionAggregation

Location/region with event count.

MetadataValueCount

Generic metadata value with count. Used in responses from:
  • /v1/metadata/event-categories
  • /v1/metadata/event-types
  • /v1/metadata/event-subtypes
  • /v1/metadata/actor-types

Source Reliability

Sources attached to events carry a reliability_tier field that classifies the origin of the source material. This value is auto-assigned by the ingestion pipeline based on the scraper type that collected the article.

Export Formats

The /v1/events/export endpoint supports multiple output formats:

CSV Format

Standard comma-separated values with headers. Includes all event fields plus actor information.

JSON Format

Array of EventDetailResponse objects with full metadata and actors.

GeoJSON Format

Geographic data format suitable for mapping applications:

ACLED Format

Compatible with ACLED (Armed Conflict Location & Event Data Project) schema. Only available for conflict category events.

Key Actor Fields

Example:

Flat Format

Denormalized JSON with actor positions as explicit columns, suitable for spreadsheet import and tabular analysis.

Actor Position Fields

Actor Position Hierarchy:
  • Principal/Secondary: Main actors in the event (actor1/actor2 in ACLED)
  • Sub-Principal/Sub-Secondary: Internal sub-units, factions, or branches within the same organization (e.g., “3rd Battalion” within “Nigerian Army”)
  • Supporting Principal/Supporting Secondary: External organizations providing support (e.g., “U.S. Special Forces” providing training to “Colombian Army”)
Example:
← Back to Taxonomy Overview