Documentation Index
Fetch the complete documentation index at: https://docs.gdeltcloud.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
API keys provide secure programmatic access to the GDELT Cloud Developer API (/api/v2/* and supported /api/v1/* endpoints). Use v2 for new integrations: Events, Stories, Entities, summaries, geo discovery, and cursor pagination.
API keys require API access on your GDELT Cloud account.
confidence_profile=precise for clean, analyst-ready results. Add confidence_profile=loose only when exhaustive/raw retrieval is required.
Generating an API Key
Create a new key
Click Create New Key and give it a descriptive name (e.g. “Production”, “Dev Environment”).
Copy your key immediately
Keys use the format:
gdelt_sk_<64-hex-chars>Example: gdelt_sk_a1b2c3d4... (64 hex characters after the prefix)Using Your API Key
Include the key as a Bearer token in theAuthorization header:
v1 endpoints remain supported for existing integrations. For new work, prefer API v2.
Rate Limits & Quotas
When you exceed a limit, the API returns HTTP429 with a machine-readable code:
| Scenario | Code | Header |
|---|---|---|
| Per-minute RPM exceeded | RATE_LIMITED | Retry-After: <seconds> |
| Monthly QU quota reached | QUOTA_EXCEEDED | — |
Retry-After header and back off accordingly:
Revoking a Key
Go to Settings → API Keys, find the key, and click Revoke. Revoked keys return HTTP401 immediately.
You can generate multiple API keys (e.g. one per environment). Each key counts against the same account quota.

