Your first message, in minutes

A clear REST API, webhooks for delivery receipts and SDKs for your languages. Everything you need to integrate messaging without friction.

Read the documentation Get an API key

Getting started

Three steps to send

Create your API key

From the dashboard, generate a secret key. Keep it server-side, never in client code.

Send a request

A POST call to /v1/messages with the channel, recipient and content. That's it.

Receive the receipts

Hook up a webhook to receive each message's status in real time: delivered, read, failed.

cURL · Send SMS / OTP

# Sending an SMS (OTP)
curl https://api.fastermessage.com/v1/messages \
  -H "Authorization: Bearer $FM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "channel": "sms",
    "to": "+221770000000",
    "from": "FasterMsg",
    "text": "Your code is 480912",
    "fallback": ["whatsapp", "voice"]
  }'

API response

200 OK · application/json

{
  "id": "msg_8a1c2e",
  "channel": "sms",
  "status": "queued",
  "to": "+221770000000",
  "created_at": "2026-06-27T12:44:01Z"
}

Webhook · delivery receipt (DLR)

POST · your endpoint

{
  "id": "msg_8a1c2e",
  "event": "message.delivered",
  "status": "delivered",
  "channel": "sms",
  "delivered_at": "2026-06-27T12:44:03Z"
}

Authentication

API key as a Bearer token, sent server-side. Key rotation, separate test and production environments.

Webhooks & DLR

Receive every status change in real time: queued, sent, delivered, read, failed. Verifiable payload signature.

SDK

Libraries for your languages: Node.js, Python, PHP, Java. List to be completed as available.

Exact endpoints, schemas and SDKs are described in the full documentation.

Ready to integrate?

Get an API key and a test environment for your first sends.

Get access