🛒 Bringo

Integrations

SMS Gateways

SMS gateways send the one-time passcodes (OTP) used for phone-number login and verification. Configure them in Admin → SMS Gateway.

📨
Built-in providers: Twilio, Vonage (Nexmo), MSG91, 2Factor.in and Fast2SMS — plus Firebase OTP, which is free and needs no SMS account. You can also add your own provider with the custom gateway builder.

General steps

  1. Open Admin → SMS Gateway.
  2. Fill in a provider's credentials (below) and save.
  3. Choose where it is used — each gateway card has toggles for Customer, Delivery, Seller and Website (global). You can send app OTPs through one provider and website OTPs through another; each target belongs to one gateway at a time.
  4. Send a test SMS — enter a mobile number in the box on the gateway card and send. This is the fastest way to prove credentials work.
💬
Message templates use #OTP# as the placeholder for the generated code (custom gateways also support #MOBILE# and #MESSAGE#).
SMS Gateway admin page
Admin → SMS Gateway.

Twilio

console.twilio.com → Account info + a Messaging sender.

Account SID
accountSid
Auth Token
authToken
Twilio number
twilioNumber — your Twilio phone number / sender id
Message
message — must contain #OTP#

Vonage (Nexmo)

API Key
vonageApiKey
API Secret
vonageApiSecret
Sender ID
smsSenderId — sender name/number
Message text
messageText — must contain #OTP#

MSG91

Auth Key
authKey
OTP template id
otpTemplateId — the DLT-approved template
Sender ID
sender (6-character DLT-approved id in India)
Route
route — transactional route (default 4)

2Factor.in

API Key
apiKey
OTP template name
otp_template_name — the approved template registered in your 2Factor account.

Fast2SMS

fast2sms.com → Dev API for the key, and your approved DLT sender/message ids.

API Key
apiKey
Sender ID
sender_id — your DLT-approved 6-character id.
Message ID
message_id — the id of the approved DLT template that carries the OTP.

Firebase OTP

Listed alongside the SMS providers, but it isn't one: the code is sent by Firebase from inside the mobile apps, so there is nothing to pay per message. It only needs your Firebase Project ID. Full setup is on the Firebase OTP page.

Add your own provider

If your provider isn't in the list, build it from the Add custom gateway form on the same page — no code required:

API URL & method
The endpoint to call, with GET, POST or PUT.
Content type
application/json, form-urlencoded or multipart.
Headers
One per line, e.g. Authorization: Bearer YOUR_KEY.
Body template
e.g. {"to":"#MOBILE#","message":"#MESSAGE#"} — the placeholders are substituted per send.
OTP message template
e.g. Your OTP is #OTP#.

Custom gateways behave like the built-in ones: assign them per audience and test them with the test-SMS box.

🇮🇳
In India, SMS senders and templates must be DLT-registered with your provider, or messages won't deliver. This is a provider/telecom requirement, not a product limitation.

Troubleshooting

OTP not received
Send a test SMS from the gateway card first — it reports the provider's own error. Then check the account balance, that the gateway is assigned to the right target (Customer / Delivery / Seller / Website), and that the sender and template are approved.
Works in the app but not on the website (or vice-versa)
Those are separate assignments. The website uses the Website (global) toggle; each app uses its own toggle.
Wrong country format
Ensure numbers include the correct country/dial code.
👉
Next: Firebase OTP — a free alternative to SMS providers.