Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developers.vfbulk.ie/llms.txt

Use this file to discover all available pages before exploring further.

​
Send a campaign

Use POST /api/v2/Campaign to send a message to one or more recipients. 
curl -X POST https://api.vodafone.com/api/v2/Campaign \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Hello from Vodafone Bulk Text!",
    "from": "Vodafone",
    "recipientInfo": [
      { "msisdn": "353861234567" }
    ]
  }'
Response:
Campaign response
{
  "success": true,
  "message": "Campaign scheduled",
  "errors": []
}

​
Multiple recipients

Multiple recipients payload
{
  "text": "Your order is on the way!",
  "from": "Vodafone",
  "campaignName": "Order Notifications",
  "recipientInfo": [
    { "msisdn": "353861234567", "notifyId": "order-001" },
    { "msisdn": "353871234567", "notifyId": "order-002" }
  ]
}
The notifyId field is echoed back in webhooks and DLRs, letting you match every callback to the right record in your system. See notifyId for use cases and full flow examples.

​
Partial delivery

If a campaign contains a mix of valid and invalid numbers, the valid numbers will still be sent to — the request is not rejected as a whole. Invalid numbers are skipped and reported in the errors array of the response. Always check the response payload to identify any numbers that failed validation.

​
Recipient limit

A single campaign request supports up to approximately 400,000 recipients. For very large sends, split your audience into batches below this limit.

​
Schedule for later

Add a sendAt timestamp (UTC) to schedule the campaign:
Scheduled campaign payload
{
  "text": "Don't miss our sale tomorrow!",
  "from": "Vodafone",
  "recipientInfo": [
    { "msisdn": "353861234567" }
  ],
  "sendAt": "2030-06-01T09:00Z"
}

​
Phone number format

FormatAccepted
Irish with prefix353871234567 ✓
Irish with leading zero0871234567 ✓
UK447911123456 ✓
Other internationalMust include country code ✓

​
Message length & credits

SMS messages are billed per message part. Understanding how parts work helps avoid unexpected credit usage.
LengthParts
1–160 chars1 part
161–306 chars2 parts
307–459 chars3 parts
460–612 chars4 parts
Messages longer than 4 parts are not supported.
Long messages are delivered as a single seamless message on the recipient’s device — they will not see separate parts.

​
Unicode characters

The API supports Unicode, which includes characters outside the standard GSM alphabet — accented characters (é, ü, ñ), non-Latin scripts, and emojis.
Unicode reduces the characters per part. A standard SMS holds 160 GSM characters, but only 70 Unicode characters per part. A short message with a single emoji can consume 2–4 credits.Additionally, some Unicode characters — particularly emojis — may not display correctly on all handsets. For reliable delivery, stick to standard GSM characters where possible.

​
Sending hours

There are no system-enforced sending hour restrictions. However, you are responsible for adhering to Irish marketing regulations — see Compliance for details.

​
Limits & billing

There are no rate limits on API calls themselves. Throughput is governed by:
  • Payload size — very large batches may take longer to process
  • Account credits — messages will not be sent if your account has insufficient credit
  • Billing tier — contact bulktext.ie@vodafone.com for details on your account limits
Last modified on May 6, 2026