API documentation

Base URL: http://www.apimassive.com/api/v1

Authentication

For direct sending use your API key (Account area) as a Bearer token. For campaign endpoints use the campaign ingest token.

Authorization: Bearer API_KEY

Campaign trigger (used by your CRM)

POST /api/v1/trigger/{ingest_token}

curl -X POST http://www.apimassive.com/api/v1/trigger/ing_xxx \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer ing_xxx" \
  -d '{
    "customer": { "phone": "+391234567890", "name": "Mario" },
    "order":    { "id": "ORD-1001", "total": "49.90" }
  }'

The platform applies the field mapping and template configured by the campaign and sends the message.

Direct send

POST /api/v1/messages

curl -X POST http://www.apimassive.com/api/v1/messages \
  -H "Authorization: Bearer API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "channel": "sms",
    "provider": "nexa",
    "to": "+391234567890",
    "text": "Hello! Your order is confirmed."
  }'

Message status

GET  /api/v1/messages/{id}     (Bearer API key)
GET  /api/v1/balance
GET  /api/v1/health

Delivery report (provider webhook)

POST /api/v1/dlr/{provider} — received from providers (Twilio, NEXA) and forwarded to the campaign callback_url.