Relayion
← Use cases
Auth

2FA codes & OTPs

OTP delivery over SMS is sensitive to timing and number consistency. Shared carrier pools mean codes can arrive from numbers users do not recognise, which increases abandonment. A dedicated SIM with a single, consistent number avoids this.

SMS · OUTBOUND
Your code is 887-204. Expires in 5 minutes.
✓ Dispatched

When a user requests a verification code, your system sends an outbound message request. Relayion dispatches it to the paired device. The SIM sends it. The user receives the code from a number they've seen before, not a rotating short code from a shared pool.

For applications where delivery speed matters, Relayion supports multi-SIM targeting. If you have a second device as a backup, you can target a specific SIM slot or a different device entirely. Your retry logic decides when to fall back and the API supports it either way.

Authentication codes are time-sensitive. Relayion provides webhook events for dispatch, delivery, and failure so your system knows whether the code reached the user or whether a retry is warranted, without polling.

One device, one SIM, one number. No shared infrastructure between your users and anyone else's.

Send a one-time code
POST /api/v1/outbound HTTP/1.1
Authorization: Bearer rlyn_bfb4d3c9…
{
"recipientNumber": "+49 30 555 01234",
"body": "Your verification code is 887-204.
It expires in 5 minutes."
}
// Delivery confirmed via webhook
{ "event": "outbound.delivered", "data": { "id": "msg_…" } }
More use cases

Ready to connect your first device?

Free plan. One device, 500 messages per month. No credit card required.

Get started free →Read the docs