MSG91 API changes, once your SMS Content Templates are approved on DLT platform
As per the latest DLT guidelines, to send an SMS, first you have to register your SMS Content Templates on the DLT platform and once your SMS Templates are registered on the DLT Platform, the next step will be to pass the DLT Template Id parameter along with the SMS.
For this, you have to follow this help doc to make the necessary changes in MSG91 API or Panel-
A. For Transactional SMS:
1. If you are using OneAPI (Send SMS via Flow) of MSG91 (https://api.msg91.com/api/v5/flow/), you do not need to bother your developer; you just need to add the DLT Template Id against the DLT approved Template on MSG91 panel.
MSG91 will forward this DLT Template Id to Telecom Operators, if you submit SMS through that Flow.
API Doc- https://docs.msg91.com/collection/msg91-api-integration/5/send-sms-via-flow/T29N6CRT
Help Doc- https://help.msg91.com/article/303-how-to-create-flow-id-to-send-sms-via-api
2. If you are not using OneAPI and using the Send SMS API of MSG91, you will have two options to pass the DLT Template Id parameter in the MSG91 API:
a). Shift to OneAPI: We highly recommend you to shift to OneAPI, since it has multiple benefits like:
-- Multi-channel communication using a single API.
-- Real-time content changes without code changes.
-- Easy to pause your SMS campaign.
API Doc- https://docs.msg91.com/collection/msg91-api-integration/5/send-sms-via-flow/T29N6CRT
Help Doc- https://help.msg91.com/article/303-how-to-create-flow-id-to-send-sms-via-api
b). Use Send SMS API: If you are not comfortable in shifting to OneAPI, you have to pass the DLT approved Template Id parameter in the Send SMS API (except OneAPI) you are using to send SMS. This parameter is an additional parameter and you have to pass all other parameters as you are passing currently
| Parameter Name | How to find its value? | Description |
| DLT_TE_ID | DLT Template Id can be found from your DLT platform | You can pass this Numeric Id once the DLT platform approves your Template and allot you a DLT Template Id. Currently, this parameter is optional, but as per DLT, it will be LIVE by 31st Jan 2021 |
B. For SendOTP:
1. If you are using SendOTP (https://api.msg91.com/api/v5/otp?), you do not need to bother your developer; you just need to add the DLT Template Id against the DLT approved Template on MSG91 panel.
MSG91 will forward this DLT Template Id to Telecom Operators, if you submit OTP SMS through that Flow.
API Doc- https://docs.msg91.com/collection/msg91-api-integration/5/sendotp/TZ648D1Y
Help Doc- https://help.msg91.com/article/176-whereto-find-the-apis-of-send-otp-and-how-to-get-template-id
2. If you are not using updated SendOTP, you will have two options to pass the DLT Template Id parameter in the MSG91 API:
a). Shift to updated SendOTP: Since it has multiple benefits like:
-- Multi-channel communication using a single API.
-- Real-time content changes without code changes.
-- Easy to pause your OTP SMS campaign.
API Doc- https://docs.msg91.com/collection/msg91-api-integration/5/sendotp/TZ648D1Y
Help Doc- https://help.msg91.com/article/176-whereto-find-the-apis-of-send-otp-and-how-to-get-template-id
b). Use the same SendOTP API: If you are not comfortable in shifting to updated SendOTP API, you have to pass the DLT approved Template Id parameter in the API you are using to send OTPs. This parameter is an additional parameter and you have to pass all other parameters as you are passing currently
| Parameter Name | How to find its value? | Description |
| DLT_TE_ID | DLT Template Id can be found from your DLT platform | You can pass this Numeric Id once the DLT platform approves your Template and allot you a DLT Template Id. Currently, this parameter is optional, but as per DLT, it will be LIVE by 31st Jan 2021 |