Sender ID Aliasing

Auto Alias Sender ID Purchase 

The Auto Alias is a feature enabled by the Syniverse API Communication assistant application where customers can automatically purchase a Sender ID  assigning as an alias . The alias feature allows customers to use any alias as a value in the "from" field of a message request and when submitted, the Communication Assistant application calls the Sender ID purchase API and purchases a Sender ID based on the capabilities [SMS, MMS, Voice] and country of termination. Once the purchase is completed, the Sender ID is stored against the Alias.

An Alias could be your real mobile number, a name or a combination of name and number. E.g. John, Inventory-555, or 14085551212.


  • Send message with from as Alias instead of senderid
curl -X POST
 -H "Authorization: Bearer d17f79e76e30e7a0f05e6444b0bbc78a"
 -H "Content-Type: application/json" -d '{"from":"alias:Alias-28776","to":["contact:cVonTugp8dibGXnIPGdo54"],"body":"Hello World to Contact"}'


  • Update senderid with Alias:
curl -X POST -H "Authorization: Bearer d17f79e76e39e7a0f05e6444b0bbc78a"
 -H "Content-Type: application/json" -d '{"alias":"Alias-28776", "version_number":"3"}'


To avoid errors while updating senderid with Alias, the current senderid’s version_number must be provided in the API call.


To obtain the current senderid’s version number you can use the API call:


curl -X GET -H "Authorization: Bearer d17f79e76e39e7a0f05e6444b0bbc78a"
-H "Content-Type: application/json"

Which returns a response like the following:

"application_id": 2769,
"company_id": 1063,
"created_date": 1588010387604,
"last_updated_date": 1653414441369,
  "version_number": 3,
  "id": " OfX4r7DeQrh7HXXHyqb5m5",
"name": "TFN_18336672499",
"ownership": "PRIVATE",
"class_id": "COMMERCIAL",
"type_id": "TOLLFREE",
"state": "ACTIVE",
"address": "18336672499",
"message_templates": [],
"country": "USA",
"consent_managed_by": "USER",

Was this article helpful?
0 out of 0 found this helpful


Please sign in to leave a comment.