Appbrew X MSG91 OTP Sign-In

Last updated: July 20, 2026

Deliver secure login OTPs over SMS and email

1. What is it?

MSG91 is a communication provider that sends one-time-password (OTP) codes to your customers over SMS and email, powering password-free login and account verification in your app. Customers enter a code sent to their phone or inbox instead of a password — a faster, more secure way to sign in.

It plugs into Appbrew's OTP Sign-in system, so you can use MSG91 as your SMS provider, your email provider, or both. Key benefits:

  • Fast, secure, password-free login with a one-time code

  • Works over both SMS and email, with email as a fallback if SMS fails

  • Template-based messaging with your own sender IDs and domains

  • DLT-compliant for Indian senders; enabled in your app by the Appbrew team

2. Which plans is it available on?

MSG91 OTP Sign-In is available on the Pro / Pro Lens and Enterprise plans.

3. What's needed to enable it?

This integration is enabled by the Appbrew team, not self-serve. Your part is to set up your MSG91 account and share the prerequisites below with us; once we have them, we configure MSG91 as your OTP provider and switch the integration on in your app.

Please gather and share the following with Appbrew:

  1. MSG91 API Key — your MSG91 authentication key.

  2. Sender ID — the ID messages will appear to come from.

  3. Message Template — the text customers receive, with the placeholder {otp} where the code should appear. It must match the template you've registered with DLT.

  4. DLT Entity ID and Template ID — required for DLT compliance for Indian senders.

Tip: You can find your API Key, Sender ID, and DLT details inside your MSG91 account dashboard under your SMS/OTP settings. For SMS delivery in India, make sure your template is approved and DLT-registered before sharing it.

Once you've shared these details, the Appbrew team enables MSG91 in your app — there's no dashboard configuration for you to do.

5. FAQ

What details do I need from MSG91 to get started?

An API Key, Sender ID, your DLT Entity ID and Template ID (for SMS), plus an email domain, sender address, and email template ID if you plan to send OTPs by email.

What should my OTP message look like?

It must match the template you've registered with DLT, with the placeholder {otp} where the code should appear — for example: “Your login OTP for our store is {otp}.”

Can I use MSG91 for both SMS and email OTPs?

Yes. You can set MSG91 as your provider for both — just complete both the Phone Provider and Email Provider sections in the OTP Sign-in settings.

My SMS messages aren't being delivered — what should I check?

Confirm your DLT Entity ID and Template ID are entered correctly, the phone number is valid with the right country code, and your MSG91 account is active and not rate-limited.

I already have MSG91 credentials — what's next?

Share them with the Appbrew team (API Key, Sender ID, DLT Entity ID, Template ID, and your message template). Once we have these, we configure MSG91 as your OTP provider and enable it in your app.

Do I need to set this up myself in a dashboard?

No. This integration isn't self-serve — the Appbrew team enables it for you. Your part is to set up your MSG91 account and send us the prerequisites listed above; we handle the configuration in the app.