Is there a way to send magic links through SMS using Stytch?

Questions
1

Hi all,

Is there a way to send magic links through SMS using Stytch? Basically, the same as magic link functionality but not through email and instead through text?

Thanks,
Udi

2

Hey Udi,

Thanks for posting!

It looks like your existing Stytch Projects are for our B2B API, is that right?

In our B2B API, there’s currently no way to send Magic Links via SMS - we only support SMS OTP as a form of MFA.

In our Consumer API, we do have an endpoint called Embeddable Magic Links, which allows you to generate a Magic Link and send it via any method you’d like (including SMS).

That said, I’m happy to pass along the interest in an off-the-shelf SMS Magic Link MFA flow in our B2B API. Are you able to provide any additional context on your use case that I can pass along to our team? Is your B2B application primarily mobile-based?

3

Hey Matt,

Thanks for the very quick response.

Yes - that’s exactly right, we have a B2B app but we still want to generate magic links that would be sent using SMS. We have a consumer app that’s connected to a B2B web application. So we need both functionalities: both the ability to send a magic link via email, which is functionality we’re going to leverage, but also the ability to send such links through SMS.
It sounds like the only way to do this now would be to, basically, implement this on our own - create magic links and send them via SMS through another provider… or perhaps we can create a second application using the Consumer API and use that? I’ll need to check if that fits our use case.
Thanks,
Udi

4

Got it!

It sounds like the only way to do this now would be to, basically, implement this on our own - create magic links and send them via SMS through another provider

To confirm, this isn’t currently possible through Stytch - our B2B API doesn’t currently offer a way to generate arbitrary Magic Links to utilize outside of our Email Magic Links flow. We do have a feature request for this, which I’ll add a +1 to on your behalf with this context!

or perhaps we can create a second application using the Consumer API and use that?

Consumer and B2B Stytch Projects utilize separate APIs and have separate user bases, so we generally wouldn’t recommend this approach - your application would need to manage separate API keys, endpoints, and user bases for this type of flow.

Are you able to provide any additional context on the preference for SMS Magic Links over SMS OTP codes that I can provide to our team?

5

It sounds like there are really two options: One that we implement this on our own and Two, that we use both B2B and Consumer applications in order to get this functionality.

Just to give additional context: We’re building an application that will allow service providers to manage a certain process for their own clients. The service providers will be using a web application whereas their clients will be using a mobile app. We’ve determined that the best way to initialize users to the service providers would be through the existing email magic link functionality. Because their clients will be using an app, we realize that it’s best that new users are initialized through SMS, which is why we we would need to be able to send a magic link via SMS. The more I think about it, the more it seems obviously we should be using both a B2B and a Consumer app; where’s no inherent barrier to doing that through Stytch, right?

Thanks,
Udi