African Countries API

Africa API gives you a clean starting point when your product needs country-level data across Africa.

Use this route family when you need:

• country directories and country pickers
• country detail pages
• compact country profiles for dashboards or reports
• current country snapshots that mix reference data with fresh signals

Start With These Endpoints

Example: List Countries In A Region

curl "https://api.africa-api.com/v1/countries" \
  -G \
  -d "region=west" \
  -d "sort=name" \
  -d "paginate=true" \
  -d "per_page=10" \
  -H "Authorization: Bearer $AFRICA_API_KEY"

Use this when you need a filtered country list for navigation, search, onboarding, or market coverage views.

Example: Get A Country Profile

curl "https://api.africa-api.com/v1/countries/ke/profile" \
  -H "Authorization: Bearer $AFRICA_API_KEY"

This is usually the best first call for a country overview page because it gives you a curated summary without making several separate requests.

Example: Get Current Country Signals

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

Use signals when your product needs a fresher operational snapshot across macro indicators, markets, trade context, climate context, humanitarian context, and government context.

Which Route Should You Use?

• Use /v1/countries when you need discovery and reference fields.
• Use /v1/countries/{country_code} when you need the full base country record.
• Use /v1/countries/{country_code}/profile when you want one curated summary payload.
• Use /v1/countries/{country_code}/signals when you care about current context more than a static record.
• Use /v1/data when you need specific indicators or time series rather than a country-centered summary.

What You Can Build

• country profile pages
• internal country research tools
• market coverage selectors
• country comparison dashboards
• onboarding flows where users choose one or more countries first

Related Docs