Skip to main content
A typical Vodafone Bulk Text integration connects your business system to the authentication service, campaign API, Vodafone messaging gateway, and callback endpoints.

​
Main components

1

Prepare recipients

Validate mobile numbers, consent status, Sender ID, and notifyId values in your own system before sending.
2

Authenticate

Request an access token. Store credentials securely and keep tokens out of browser code, logs, and analytics tools.
3

Send the campaign

Call POST /api/v2/Campaign with the message text, Sender ID, recipients, and optional schedule.
4

Receive callbacks

Accept processing webhooks and delivery receipts with 200 OK after your system records the payload.
5

Reconcile status

Match callbacks to your records with notifyId and update campaign, customer, or reporting tables.

​
Operational expectations

  • Build callback handlers to be idempotent.
  • Respond with 200 OK only after you have accepted the payload.
  • Store raw callback payloads when auditability matters.
  • Treat missing or delayed DLRs as unconfirmed until your own timeout policy expires.
  • Use Troubleshooting for common integration issues.
Last modified on May 6, 2026