Skip to main content
GET
Get country context

Authorizations

Authorization
string
header
required

GDELT Cloud API key. Send as Authorization: Bearer gdelt_sk_....

Path Parameters

iso3
string
required

The iso3.

Query Parameters

time_basis
enum<string>
default:published

Clock for date/hour filters and ordering: published preserves the serving/reference publication time; recorded uses the durable journal commit time and includes late publications when they become available. Omission retains published compatibility. Choose recorded explicitly for ongoing activity Monitors; source dates remain unchanged. Full value list: https://docs.gdeltcloud.com/reference/enums#activity-time-basis

Available options:
published,
recorded
date_start
string<date>

First UTC date in the selected time_basis. Defaults to today; future dates are rejected. Neither clock is Event occurrence time. Note: validation is owned by the endpoint service because it depends on composed or cross-parameter state; the published error semantics above still apply.

date_end
string<date>

Last UTC date in the selected time_basis, inclusive. Defaults to date_start and cannot be later than the current UTC day. Note: validation is owned by the endpoint service because it depends on composed or cross-parameter state; the published error semantics above still apply.

hour
integer

Optional UTC hour, 0–23. Requires a single date and rejects hours that have not started. The current hour is allowed and describes publications so far; omit for the whole selected day.

Required range: 0 <= x <= 23
basis
string
default:publication

publication retains the activity journal clock. reporting uses distinct served Events by occurrence date and location country (country_match=location), and Stories by reporting date under every authoritative country association (the Stories summary country_attribution=all mode). Country buckets may overlap for Stories; totals are computed independently. Reporting has day precision and rejects hour. Note: validation is owned by the endpoint service because it depends on composed or cross-parameter state; the published error semantics above still apply.

Response

Success

success
boolean
data
object