Kaleyra
Step 1. Account Setup
If you do not have an account with Kaleyra yet, create an account here. Kaleyra requires you to complete its KYC and other details to get sender id and register templates. Follow the onboarding doc here to get the setup done.
If you are sending SMSs in India, TRAI has mandated to register their business, headers (sender IDs), and templates on any of the DLT platforms. Follow the guide here to get the setup done.
Step 2. Kaleyra Integration in Raven
| Keys | Details |
|---|---|
Sender | Sender id to be sent with the SMS. Follow the steps here to get your Sender ID |
API Key | API key for your account. Follow the steps here to create one. |
SID | Account SID (Security Identifier). Generated along with the API key. To check go to Developers > Select API Key > Edit |
Route | Applicable only for SMSes sent by Indian businesses to Indian destination numbers. Use the route type specified when registering your templates. Possible values: Transactional, OTP, Promotional. |
DLT Entity ID | Applicable only for SMS sent by Indian businesses to Indian destination numbers. Your Entity Id as registered on DLT (Distributed Ledger Technology) portal of operators in India. This is mandatory to be passed in API or configured on Dashboard for SMSes towards Indian destination here |
Step 3. Delivery Reports
There is no additional configuration required to setup delivery reports. Raven manages the delivery callback internally for Kaleyra.
Advanced
Send additional parameters to Gupshup
Raven sends the fields present in the SMS template to Kaleyra by default. To send additional fields, please check our Override doc.
IP Whitelisting You can control access by specifying Raven’s IP address, or make sure Raven’s IP addresses are whitelisted and not blocked. Please check point 4 in the guide here.
IPs: 65.2.109.100, 65.2.58.233
Links