Header (Sender ID) Registration

please note before performing this step, you will need to ensure that you've completed the mandatory entity registration on the operator’s website if that is not complete, please refer to this article to get an overview of how that is done also, it is advised to have a basic understanding of the categorization of sms this will help you decide what category of sender id you need to seek approval for click here to understand the different types of sms there are 2 important changes to note with respect to senderid registration 1\) as per the new regulation, only otp messages for banks are considered transactional all other otp messages or transactional messages are classified as service implicit while creating the sender ids (for non banking related use cases), you need to use service implicit as the type for senderid 2\) promotional messages need a numeric sender id please note that while creating promotional headers on the portal, the header should start with the number that matches the category (as per dnd preferences) 1 banking/insurance/financial products/ credit cards e g 110011 2 real estate e g 220022 3 education e g 330033 4 health e g 440044 5 consumer goods and automobiles e g 550055 6 communication/broadcasting / entertainment/it e g 660066 7 tourism and leisure e g 770077 8 food and beverages e g 880088 if an enterprise registers itself under the category ‘tourism’, they can register their headers as 712390, 790234, 791919 a health based company should register its headers as 412300, 490909, etc sample walkthrough of senderid registration here sending sms via exotel with your registered headers (sender ids) once your headers are registered and approved, follow the below instructions to send sms for promotional sms once added and accepted by our system, use the numeric sender id or linked exophone in the ‘from’ field of sms api similarly, select the appropriate sender id for your campaigns sms delivery will only work if the numeric sender id (header) is configured correctly with exotel and approved on dlt platforms for transactional sms once approved by the dlt platforms, update the sender id if not already linked to one of your exophones via the sms configuration section once added and accepted by our system, use the alpha sender id or linked exophone in the ‘from’ field of sms api if you are sending sms via api and you don’t have a valid sender id configured against the sms body (transactional or promotional), your api request will fail with `400 http error code` example request curl x post https //\<your api key> \<your api token>\<subdomain>/v1/accounts/\<your sid>/sms/send \ d "from=600xxx" \ d "to=xxxxx30240" \ d "body=hello world!" for promotional sms body, numeric sender id 600xxx should be approved by the dlt platform and configured with an exophone on exotel similarly, replace ‘from’ with alpha sender id for transactional sms body present in your account like ‘exotel’ to avoid delivery failures refer here for more information on api sms delivery will only work if transactional alpha sender id or numeric sender id (header) is used correctly for your sms request via exotel and approved on the dlt platforms of the operator watch a short video