african stock market apiafrican stock exchange apiafrica stock apipan-african stock data api

African Stock Market API for Multi-Exchange Data

*Last updated: May 13, 2026 | Reading time: ~10 minutes*

March 21, 2026 · 7 min read · Mansa Markets

Last updated: May 13, 2026 | Reading time: ~10 minutes

If you are searching for an African stock market API, the real challenge is not finding one exchange feed. It is finding one product that lets you work across African markets without stitching together separate scrapers, currencies, schemas, and exchange-specific quirks.

That is what Mansa API is built for.

Mansa API gives you one REST API for African market data across 20 tracked exchanges, including the Nigerian Exchange, Ghana Stock Exchange, Nairobi Securities Exchange, Johannesburg Stock Exchange, BRVM, Dar es Salaam Stock Exchange, Lusaka Securities Exchange, Egyptian Exchange, and more. Instead of integrating one country at a time, you get a unified market data layer for exchange snapshots, listed stocks, movers, indices, forex, commodities, and exchange metadata.

If you are building a fintech app, research dashboard, brokerage tool, market screener, media product, or AI workflow around African capital markets, this is the page to understand what the API covers and how the endpoints fit together.

## Why an African Stock Market API Is Hard to Build Internally

Most teams start with one market. Then the product roadmap expands.

You launch with Nigeria. Then users ask for Ghana. Then Kenya. Then South Africa. Very quickly, the internal problem stops being “How do we get prices?” and becomes:

How do we normalize data across multiple exchanges?
How do we handle different trading calendars and market hours?
How do we maintain ticker, currency, and exchange metadata consistently?
How do we compare movers across markets without building custom logic per country?
How do we ship all of this without maintaining a fragile scraper fleet in-house?

That is why a real African stock market API should not just expose one stock list endpoint. It should give you a consistent cross-market system.

## What Mansa API Covers

Mansa API is designed as a pan-African market data layer. The current surface includes:

exchange coverage across 20 tracked African markets
listed stocks and per-exchange stock universes
single-stock quote endpoints
per-exchange movers
pan-African movers
African market indices
African forex rates
commodity benchmarks relevant to African markets
exchange metadata for market structure and operating context

The practical result is simple: you can build one product that covers Nigeria, Ghana, Kenya, South Africa, BRVM, Tanzania, Zambia, Egypt, and the rest of your tracked African universe without changing your response model every time you add a market.

## The Core Endpoints

The strongest feature of Mansa API is that the endpoints fit together as one market stack.

1. List all exchanges

Use this when you need the top-level market map for your product.

```http GET https://www.mansaapi.com/api/v1/markets/exchanges ```

This is the endpoint that answers:

which African exchanges are covered
what exchange codes to use
what currencies and market labels exist
what the latest exchange snapshot looks like

2. Get one exchange

Use this when you need the latest state of one market.

```http GET https://www.mansaapi.com/api/v1/markets/exchanges/{exchangeCode} ```

Examples:

`NGX`
`GSE`
`NSE`
`JSE`
`BRVM`
`DSE`
`LUSE`

This is the right endpoint for exchange overview cards, market summary pages, and exchange-specific dashboards.

3. Get stocks for one exchange

Use this to build listings tables, screeners, or sector slices.

```http GET https://www.mansaapi.com/api/v1/markets/exchanges/{exchangeCode}/stocks ```

This is the endpoint you use when you want:

all NGX-listed stocks
all NSE Kenya stocks
GSE banking names
BRVM companies sorted by price move or market cap

4. Get one stock

Use this for company detail pages and quote lookups.

```http GET https://www.mansaapi.com/api/v1/markets/exchanges/{exchangeCode}/stocks/{ticker} ```

This is the endpoint behind a page like:

`NGX / DANGCEM`
`NSE / SCOM`
`GSE / MTNGH`
`JSE / NPN`

5. Get stock history

Use this when your product needs historical price series.

```http GET https://www.mansaapi.com/api/v1/stocks/{ticker}/history ```

This is the right endpoint for:

historical charts
portfolio backtests
factor research
analyst dashboards

6. Get exchange movers

Use this to show what is moving inside one market today.

```http GET https://www.mansaapi.com/api/v1/markets/exchanges/{exchangeCode}/movers ```

This powers country-specific:

top gainers
top losers
market pulse widgets

7. Get pan-African movers

This is one of the clearest reasons to use a pan-African API rather than exchange-specific feeds.

```http GET https://www.mansaapi.com/api/v1/markets/movers/pan-african ```

This endpoint lets you compare what is moving across Africa in one call. That is useful for:

continental heatmaps
Africa-wide market dashboards
alerting products
AI research agents looking for unusual moves across markets

8. Get market indices

```http GET https://www.mansaapi.com/api/v1/markets/indices ```

This endpoint is for index boards, regional comparison views, and macro market snapshots.

9. Get forex

```http GET https://www.mansaapi.com/api/v1/markets/forex ```

This matters because African market products are multi-currency by default. If you want to compare NGX, GSE, NSE, JSE, BRVM, DSE, and LUSE performance in one product, you need currency context.

10. Get commodities

```http GET https://www.mansaapi.com/api/v1/markets/commodities ```

This is useful when your product needs the macro layer around African equities. Oil, cocoa, coffee, copper, and similar benchmarks explain a meaningful share of sector behavior in African public markets.

11. Get exchange metadata

```http GET https://www.mansaapi.com/api/v1/markets/exchange-metadata ```

This is the reference layer for:

market structure
trading hours
exchange websites
settlement context
regulator context

## What Makes This Different from a Single-Exchange API

A Nigerian stock market API solves a Nigerian problem.

An African stock market API should solve a portfolio, product, or research problem that spans multiple exchanges.

That is the real distinction.

With Mansa API, you can:

show NGX, GSE, NSE, JSE, and BRVM in one interface
rank movers across Africa, not just one country
normalize exchange coverage inside one schema
build one internal market data service instead of many fragmented ones

This is especially important for:

fintech products expanding country by country
investor dashboards with multi-market coverage
institutional research teams
financial publishers
AI and automation tools working on African securities

## Example: Building a Pan-African Market Dashboard

If your product needs an Africa-wide homepage, the natural stack looks like this:

```javascript const BASE_URL = "https://www.mansaapi.com/api/v1"; const headers = { Authorization: `Bearer ${apiKey}` };

const [exchangesRes, moversRes, indicesRes, forexRes, commoditiesRes] = await Promise.all([ fetch(`${BASE_URL}/markets/exchanges`, { headers }), fetch(`${BASE_URL}/markets/movers/pan-african`, { headers }), fetch(`${BASE_URL}/markets/indices`, { headers }), fetch(`${BASE_URL}/markets/forex`, { headers }), fetch(`${BASE_URL}/markets/commodities`, { headers }), ]); ```

That gives you:

exchange board
pan-African gainers and losers
indices strip
forex layer
commodity context

Then for each exchange page, you add:

```javascript await Promise.all([ fetch(`${BASE_URL}/markets/exchanges/${code}`, { headers }), fetch(`${BASE_URL}/markets/exchanges/${code}/stocks`, { headers }), fetch(`${BASE_URL}/markets/exchanges/${code}/movers`, { headers }), ]); ```

Then for stock pages:

```javascript await Promise.all([ fetch(`${BASE_URL}/markets/exchanges/${code}/stocks/${ticker}`, { headers }), fetch(`${BASE_URL}/stocks/${ticker}/history`, { headers }), ]); ```

That is a coherent African stock market product architecture, not a pile of one-off exchange integrations.

## Best Use Cases

The developers most likely to search for an African stock market API are usually building one of these:

Fintech apps

You want one API that can support expansion from Nigeria into Ghana, Kenya, South Africa, and beyond without rebuilding your data layer every time.

Investor dashboards

You want market overview pages, per-exchange tables, company pages, movers boards, and macro context inside one product.

Media and publishing

You want African stock data embedded in articles, newsletters, and editorial dashboards without running your own scraper stack.

Institutional research

You want a cleaner way to access multiple African equity markets in one normalized interface.

AI and automation

You want LLMs, agents, and internal tools to query market state, movers, exchange lists, and stock detail data in a predictable format.

## Authentication

Authentication uses a Bearer token.

```http Authorization: Bearer mansa_live_sk_xxxxxxxxxxxxxxxxxxxxxxxx ```

To request access, go to Mansa API Developers.

## Why the Blog Post Matters

This page is intentionally a blog post and not just a generic docs page.

That is because the keyword `african stock market api` has both informational and commercial intent. People searching it are usually trying to understand:

whether such an API exists
what exchanges it covers
whether it supports their use case
how the endpoints are structured
whether it is worth integrating

So this page should rank for the search, explain the product clearly, and then send the highest-intent readers to the developers page.

## Get Started with Mansa API

If you need an African stock market API that goes beyond one country, Mansa API is the right positioning:

one API
20 tracked exchanges
exchange snapshots
stock lists
stock detail
movers
pan-African movers
indices
forex
commodities
exchange metadata

Start here:

If you are building an African investing app, research product, data terminal, screener, or AI workflow, this is the product category page you should benchmark against.