A browser API workbench for quick checks, sandbox calls, webhook debugging and African API exploration. Build requests, swap environments, import cURL, run assertions, save useful calls and export code.
Variables are replaced in URLs, headers and bodies with the baseUrl and token variable names, provider secrets, and African API keys. Only non-secret values can be saved. Credentials stay in memory and are cleared after send, cancel or page exit.
Send a request to see the response body here.
Generic API testers are useful, but African developers often need to jump between local services, fintech sandboxes, USSD callbacks, mobile money authentication, identity providers and deployment constraints. This tool keeps the quick browser workflow while adding environments, presets, cURL export and saved requests for repeat debugging.
Use the built-in same-origin AfroTools status endpoint for a first browser-safe test, then switch to templates for Paystack, Flutterwave, M-Pesa Daraja, MTN MoMo and Africa's Talking. Some production APIs intentionally reject browser-origin requests. That is not a tool failure. It is a security rule, and the cURL export gives you a safer terminal path for those requests.
Browsers block responses from APIs that do not allow your page origin. If the API is not browser-enabled, copy the generated cURL command and run it from a terminal or backend service.
No. Credentialed requests are sent only after you confirm the exact endpoint. AfroTools blocks credentialed sends to its own domains and telemetry routes, does not proxy the request, and never stores secret values. Saved requests and code previews keep redacted placeholders only.
Use it for quick browser checks, sandbox templates, cURL generation, classroom demos and lightweight debugging. For team workspaces, secrets vaulting and automated CI collections, a full API client is still better.