Message history & receipts

Every send with its full lifecycle — including read receipts, which SMS can never give you.

GEThttps://api.mobilesasa.com/api/v1/whatsapp/messages

Query parameters

FieldTypeRequiredDescription
account_uuiduuidNoFilter to one connected account.
statusstringNoOne of queued, sent, delivered, read, failed.
searchstringNoMatch against recipient numbers.
page / page_sizeintNoStandard pagination.
curl "https://api.mobilesasa.com/api/v1/whatsapp/messages?status=read&page=1" \
  -H "Authorization: Bearer $MOBILESASA_TOKEN"
Response
{
  "success": true,
  "data": {
    "messages": [
      {
        "uuid": "7c31…",
        "msisdn": "254712345678",
        "template_name": "statement_ready",
        "status": "read",
        "cost": 1.2,
        "created_at": "2026-07-10T09:32:11Z"
      }
    ],
    "total": 412,
    "page": 1,
    "page_size": 50
  }
}

Status lifecycle

  • queued — accepted, awaiting dispatch to Meta.
  • sent — accepted by WhatsApp.
  • delivered — reached the recipient's device.
  • read — blue ticks; the recipient opened it.
  • failed — not deliverable (not a WhatsApp user, policy rejection, expired token…). The reason is recorded on the message.

Statuses update in near-real time as Meta's webhooks arrive — poll this endpoint or reconcile in batches, whichever suits your system.