The GDELT Cloud Developer API (/api/v1/*) provides programmatic access to GDELT event data starting from January 2025, with historical coverage expanding over time and new data updated hourly. Use it to fetch media event clusters, entity profiles, and news domain data from your own applications and scripts.
Media Events
Top news stories clustered from articles, filterable by category, country, and event type
Entities
Wikipedia-linked GEG entity profiles with sentiment, linked stories, and relationship graph
Domains
News domain profiles — stats, top persons/orgs, recent articles
Complete data with per-article metrics, full integration (default)
Copy
# Compact summary cards for quick scanningGET /api/v1/media-events?days=1&limit=10&detail=summary# Standard detail with article linksGET /api/v1/media-events?days=7&limit=5&detail=standard# Full data (default, backward-compatible)GET /api/v1/media-events?days=1&limit=10&detail=full
summary returns compact headline cards: cluster_id, label, category, scope, time_bucket, article_count, avg_goldstein, avg_tone, quad_class, event_description, location, top 5 entity names, top 5 source domains, and languages.standard adds trimmed representative articles (URL, title, domain, date, weight), resolved actor/event/location details, and top 10 linked entities.full (default) returns the complete unmodified response including per-article metrics, all linked entities, and lat/long coordinates.
Use filters to explore specific angles of a story:
Copy
# How is China involved in this story?GET /api/v1/media-events/cluster?cluster_id=abc123&actor_country=CHN# French-language coverage onlyGET /api/v1/media-events/cluster?cluster_id=abc123&language=fr# Only Reuters articlesGET /api/v1/media-events/cluster?cluster_id=abc123&domain=reuters.com
When filters are applied, the response includes filtered_count showing how many articles match.
Always pass date and days matching the media-events discovery call to ensure efficient partition-scoped queries.
The search parameter enables natural-language semantic search across media event clusters. When provided, clusters are ranked by embedding similarity (cosine distance) instead of article count.
Copy
# Find stories about AI regulationGET /api/v1/media-events?search=AI+regulation+European+Union&detail=summary# Semantic search + category filterGET /api/v1/media-events?search=trade+war+tariffs&category=economy_business&detail=summary# Semantic search + actor country + locationGET /api/v1/media-events?search=nuclear+negotiations&actor_country=IRN&location=US&detail=summary# Semantic search over a weekGET /api/v1/media-events?search=climate+change+protests&days=7&detail=summary
All filters work with search — they combine as AND (each filter narrows results):
Filter
Works with search?
How it’s applied
date / days
✅
Time window constraint
category
✅
Cluster-level pre-filter
scope
✅
Cluster-level pre-filter
actor_country
✅
Event-level pre-filter (restricts article candidates before ANN)
event_type
✅
Event-level pre-filter
location
✅
Event-level pre-filter
language
✅
Language pre-filter
domain
✅
Domain pre-filter
goldstein_min/max, tone_min/max, quad_class
✅
Post-resolution filter
Semantic search is best for conceptual queries — topics, themes, or ideas described in natural language. Use structured filters for precise criteria like specific countries, event types, or date ranges. Combine both for the most targeted results.