Skip to main content
Send Bulk SMS (POST)
curl --request POST \
  --url https://api.example.com/api/v2/SendBulkSMS \
  --header 'Content-Type: application/json' \
  --data '
{
  "SenderId": "<string>",
  "Messages": [
    {}
  ],
  "Messages[].Number": "<string>",
  "Messages[].Text": "<string>",
  "ApiKey": "<string>",
  "ClientId": "<string>"
}
'
{
  "ErrorCode": 123,
  "ErrorDescription": "<string>",
  "Data": [
    {}
  ],
  "Data[].MobileNumber": "<string>",
  "Data[].MessageId": "<string>"
}

​
Send Bulk SMS (POST)

Send bulk SMS messages using the POST method with a JSON request body. This method is recommended for sending different messages to different recipients. 
curl -X POST "https://accounts.netvox.ng/api/v2/SendBulkSMS" \
  -H "Content-Type: application/json" \
  -d '{
    "SenderId": "YOUR_SENDER_ID",
    "Is_Unicode": true,
    "Is_Flash": false,
    "SchedTime": "",
    "Messages": [
      {
        "Number": "1234567890",
        "Text": "Hello John, your order is ready!"
      },
      {
        "Number": "0987654321",
        "Text": "Hello Jane, your appointment is tomorrow at 2 PM"
      }
    ],
    "ApiKey": "YOUR_API_KEY",
    "ClientId": "YOUR_CLIENT_ID"
  }'

​
Request Body

​
SenderId
string
required
Approved sender ID for the messages
​
Messages
array
required
Array of message objects
​
Messages[].Number
string
required
Mobile number for the message
​
Messages[].Text
string
required
Message text content
​
ApiKey
string
required
Your API key for authentication
​
ClientId
string
required
Your client identifier for authentication
​
Is_Unicode
boolean
Set to true for Unicode messages (default: false)
​
Is_Flash
boolean
Set to true for flash messages (default: false)
​
SchedTime
string
Schedule time in yyyy-MM-dd HH:MM format (optional)

​
Response

​
ErrorCode
number
Error code (0 for success)
​
ErrorDescription
string
Description of the result
​
Data
array
Array of message results
​
Data[].MobileNumber
string
Mobile number that received the message
​
Data[].MessageId
string
Unique message ID for tracking

​
Success Response

{
  "ErrorCode": 0,
  "ErrorDescription": "Success",
  "Data": [
    {
      "MobileNumber": "7894561230",
      "MessageId": "fc103131-5931-4530-ba8e-aa223c769536"
    },
    {
      "MobileNumber": "7894561231",
      "MessageId": "f893293d-d6ea-45e8-b543-40f0df28e0c9"
    }
  ]
}

​
Message Examples

​
Personalized Notifications

{
  "Messages": [
    {
      "Number": "1234567890",
      "Text": "Hi John, your order #12345 has been shipped!"
    },
    {
      "Number": "0987654321",
      "Text": "Hi Sarah, your order #12346 is ready for pickup!"
    }
  ]
}

​
Appointment Reminders

{
  "Messages": [
    {
      "Number": "1234567890",
      "Text": "Reminder: Your dental appointment is tomorrow at 10:00 AM"
    },
    {
      "Number": "0987654321",
      "Text": "Reminder: Your doctor appointment is tomorrow at 2:30 PM"
    }
  ]
}

​
Marketing Campaigns

{
  "Messages": [
    {
      "Number": "1234567890",
      "Text": "Hi John! Get 20% off your next purchase. Use code: SAVE20"
    },
    {
      "Number": "0987654321",
      "Text": "Hi Sarah! New arrivals in your favorite category. Shop now!"
    }
  ]
}

​
Use Cases

  • Personalized messaging: Send different messages to different recipients
  • Marketing campaigns: Targeted messages for different customer segments
  • Notifications: Different notification types for different users
  • Appointment reminders: Personalized reminders with specific details
  • Order updates: Different status updates for different orders
  • Event invitations: Personalized invitations with different details

​
Best Practices

  1. Batch size: Keep batch sizes reasonable (100-500 messages per request)
  2. Error handling: Handle individual message failures gracefully
  3. Rate limiting: Respect API rate limits for bulk operations
  4. Message validation: Validate message content before sending
  5. Personalization: Use recipient data to personalize messages