Nukta AI API Platform is the Tanzania developer hub for public data APIs. Don’t struggle to scrape us — integrate with us. Get Bank of Tanzania and commercial bank forex, DSE snapshots, bidhaa prices, investment offers and fundamentals, price histories, bank products, mobile wallets, discover posts, and similar news as JSON. Built for fintech, media, and startup developers in Dar es Salaam and across East Africa. Tell us what you’re working on and we’ll help enrich your data. Open a playground, send a GET request, and copy cURL or fetch starters into your app.
Popular searches these APIs answer
Tanzania API, Tanzania developer API, public API Tanzania, REST API Tanzania, JSON API Tanzania, fintech API Tanzania, Dar es Salaam API, East Africa API, scrape Tanzania data, do not scrape use API, integrate instead of scrape, web scraping alternative Tanzania, developer API playground, Tanzania open data API, Nukta AI API, BoT forex API, DSE API, bidhaa prices API, Tanzania news API, TZS exchange rate API, Tanzania banks API, mobile money API Tanzania, fundamentals API Tanzania, price history API Tanzania, Tanzania MCP API, Model Context Protocol Tanzania, public MCP server
FAQ for Tanzania API developers
Should I scrape Nukta AI or use the API?
Please don’t scrape us — integrate with us. Public Data APIs give Tanzania developers stable JSON for forex, DSE stocks, commodities, offers, banks, mobile wallets, and news. Scrapers break when HTML changes; APIs are the supported path.
Is there a public API for Tanzania forex and DSE data?
Yes. Nukta AI exposes GET APIs for Bank of Tanzania and bank FX rates (CRDB, NMB, KCB), forex movers, DSE gainers/losers, and market summary — designed for developers building fintech and market tools in Tanzania.
Who is the Nukta AI API Platform for?
Developers, fintech teams, news product builders, data analysts, and startups in Tanzania and East Africa who need JSON market and content data without maintaining web scrapers.
Do I need an API key for Nukta AI Data APIs?
No. Tier A public GET endpoints under /api/* work without a key when called from the same Nukta AI host. Partner API keys are planned for higher-volume or off-origin access.
Which Tanzania data can I fetch from the API Platform?
Public playgrounds cover forex rates (BoT, CRDB, NMB, KCB), forex movers, commodities (bidhaa), DSE gainers/losers, market summary, daily prices, price histories, fundamentals, investment offers, banks (cards/fees/accounts), mobile wallets, communities (topics/threads/messages), iTrust ETF, asset allocation, topics, discover posts, and similar news. The same catalog is available read-only via Public MCP at POST /api/public/mcp.
Is there a public MCP (Model Context Protocol) endpoint?
Yes. POST /api/public/mcp is a keyless, rate-limited, read-only MCP server for Tanzania public Data APIs. Docs and Cursor examples live at /api-platform/mcp. Full partner CRUD remains on authenticated POST /api/mcp.
Can Tanzania developers use this instead of scraping bank or DSE websites?
Yes for the datasets we publish. Integrate our JSON endpoints for forex, DSE snapshots, bidhaa prices, bank products (/api/banks), mobile wallets (/api/mobile_wallets), and related feeds rather than scraping bank or exchange HTML. If you need more series, email us and we can discuss enrichment.
What is the difference between Search API and Data APIs?
Data APIs are read-only JSON feeds for news, markets, and discover. Search API is a separate semantic search product surface. Agent API is for conversational agents with structured messages.
Can I use these APIs in a mobile app?
Yes for public reads, subject to fair use and future rate limits. Prefer server-side fetching for any secrets, and cache responses where appropriate — a common pattern for Tanzania fintech and news apps.
How do we partner if we need more data?
Email danny@nukta.co.tz with what you’re working on and which feeds you need. We’ll help explore integration options and enrich your data where we can.
Why do playground request URLs start with /api/...?
Playgrounds use relative paths so they hit the environment you are browsing (local or production). Prepend your site origin when calling from external scripts.