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.

Use this page to diagnose common authentication, campaign, Sender ID, and callback issues.

Authentication issues

SymptomLikely causeFix
401 Unauthorized from the APIMissing, expired, or invalid access tokenRequest a new token and retry the API call.
invalid_grant from the token endpointIncorrect username or passwordCheck the credentials supplied for the Bulk Text account.
Token expires during processingAccess tokens are short-livedRe-authenticate before requests or retry once after 401.
Request is rejected by the token endpointWrong content type or form bodySend application/x-www-form-urlencoded with grant_type=password and client_id=ismstoken.
See Authentication for complete examples.

Campaign request issues

SymptomLikely causeFix
415 Unsupported Media TypeRequest is not JSONSend campaign requests with Content-Type: application/json.
Message is not acceptedMissing required fieldInclude text, from, and at least one recipientInfo entry.
Some recipients are skippedInvalid recipient numbersReview the errors array and correct the affected msisdn values.
Account has no creditsMessage processing returns a credit errorAdd credit or contact bulktext.ie@vodafone.com.
Scheduled message does not send when expectedsendAt is not UTC or has the wrong formatUse UTC in yyyy-MM-ddTHH:mmZ format.

Sender ID issues

SymptomLikely causeFix
Sender is not validfrom is not approved on the accountCall GET /api/v2/senderlist and use one of the returned values.
Irish recipients do not receive messagesInternational non-ComReg Sender ID used for Irish trafficUse a Type 0 ComReg Sender ID or Type 2 numeric Sender ID.
New Sender ID is unavailableRegistration is not completeContact bulktext.ie@vodafone.com.

Callback issues

SymptomLikely causeFix
No webhook arrivesCallback URL is not configuredSend your HTTPS endpoint to bulktext.ie@vodafone.com.
Vodafone cannot deliver callbacksEndpoint does not accept POST or TLS requirements are not metEnsure your endpoint accepts POST, supports TLS 1.2 where required, and returns 200 OK.
Duplicate callback processingHandler is not idempotentStore callback IDs or use notifyId plus timestamp/status to deduplicate.
DLR arrives lateMobile network delivery status is delayedAccept late DLRs and keep messages in an unconfirmed state until your timeout expires.
Verification hash does not matchWrong verification key or hash inputCheck the documented formula and confirm the verification key for your account.

Legacy API issues

The v1 URL-encoded API returns plain-text status codes and messages, sometimes inside a 200 OK HTTP response. Always inspect the response body before treating the request as successful. See Legacy API overview and the URL-encoded legacy endpoint in the Legacy APIs sidebar.
Last modified on May 6, 2026