Introduction
Build messaging, notification, campaign, and verification workflows on top of NairaSMS using a dedicated public API runtime.
Basics
NairaSMS APIs are organized around REST endpoints, JSON payloads, scoped API keys, and predictable response objects. You can send SMS, create bulk campaigns, request sender IDs, check wallet balance, and verify SMS OTPs without sending traffic through the customer dashboard runtime.
Developer traffic uses wallet balance. This keeps public API billing separate from the SMS credit workflow used inside the main NairaSMS dashboard.
Start with authentication, create a scoped key, then test with a small SMS request before moving to campaign endpoints. Every protected request returns a requestId that can be used for support and audit tracing.
Testing
Use Postman, Insomnia, cURL, or your preferred HTTP client. Keep separate API keys for development and production, and grant only the scopes an integration needs.
API Endpoint
Use the versioned base URL below for every request in these docs.
https://api.v1.nairasms.com.ng/v1Explore Products
Messaging->
Deliver transactional alerts, customer notifications, and bulk SMS campaigns from one API.
Token->
Generate and verify one-time passwords for logins, checkouts, onboarding, and transaction approvals.
Sender IDs->
Request branded sender names and check approval status before going live.
Campaign Reports->
Fetch campaign history, inspect delivery status, and reconcile message activity.
Wallet Balance->
Check the wallet balance used by developer API traffic before sending.