African data, one API

African data for real products and integrations.

Country reference data, current signals, historical indicators, official FX and market layers, trade, and government records through one consistent REST API.

$ curl https://api.africa-api.com/v1/countries/ke/profile -H "Authorization: Bearer $AFRICA_API_KEY"[]
54Countries
127Indicators
8Domains
10yr+Historical data

Start with the route that matches the job

The platform is organized around a small set of endpoint families. Learn the conventions once, then move from reference data to current signals, historical series, trade, markets, and government records without changing your client model. Popular entry points include Countries, Agriculture, and Policies.

Also live

CountriesLive

A reliable country layer for discovery, profiles, and product-ready records across all 54 African countries.

/v1/countries
capitalregioncurrencieslanguagesprofile
DataLive

A consistent query layer for historical indicators, latest values, and comparison-ready time series.

/v1/data
country_codemetric_keyyearlatestsource
IndicatorsLive

Discover what data exists, where coverage is strong, and which metrics are ready for rankings and analysis.

/v1/indicators
categoryhas_datacoveragerankings
TradeLive

Bring country trade overviews, partner flows, and product flows into research and commercial products.

/v1/trade/*
overviewflowspartnersproducts
GovernmentLive

Track leaders, terms, cabinets, elections, and policy timelines through one connected government domain.

/v1/government/*
overviewleaderstermscabinet
PoliciesLive

Access laws, policy documents, lifecycle events, and policy timelines in a structure built for search and monitoring.

/v1/policies/*
countrydocument_typestatusevents
MarketsLive

Bring exchange metadata, tickers, price history, and FX rates into African market products.

/v1/markets/*
exchangestickershistoryfx-rates
GeographiesLive

A clean geography layer for continent, region, subregion, and country hierarchy across the platform.

/v1/geographies
typeparent_keycountry_codeq

How it works

From first request to production integration.

1

Get an API key

Create an account in the dashboard, generate a key once, and reuse the same bearer-token pattern across the platform.

2

Start with a high-value request

Start with signals for a useful country snapshot, use profiles for a curated reference summary, or use `/v1/data` when you need explicit metric and time-series queries.

curl -H "Authorization: Bearer $AFRICA_API_KEY" https://api.africa-api.com/v1/countries/ng/signals
3

Go deeper when you need it

Add trade, markets, elections, policies, or source-level metadata as your application grows. The reference docs show the available options and query patterns.

Built for integration

The product choices behind the public API surface.

Stable contracts

Public routes live behind stable /v1 paths and are designed to evolve additively.

Clear route boundaries

Reference data, signals, historical observations, markets, trade, and government records each have a clear place in the API.

Historical plus current

Use /v1/data for long-run series and /v1/countries/{country_code}/signals for the latest country snapshot.

Consistent authentication

Most data routes use the same bearer-token pattern so you can reuse one client across the platform.

Traceable when it matters

Source, freshness, and quality details are available when you need to validate data in production.

Start with the route that matches the product job

Use quickstart to get authenticated, coverage to see what is live by country and domain, signals for a compact country snapshot, or data for explicit metric queries.