Integrations
SIMRelay slots into the tools your team already uses, with one or two minutes of setup per integration. You don't have to live in our dashboard — you can, but the more common pattern is to wire SIMRelay into Slack / Teams / email and never log in unless something needs configuring.
Slack
OAuth flow grants SIMRelay permission to post into channels your team selects. From there, each number can be mapped to one or more channels. Test the integration from the dashboard before you trust it with real verification codes.
Microsoft Teams
Uses Microsoft's Incoming Webhook connector. Generate the connector URL inside the Teams channel, paste it into the SIMRelay dashboard, and incoming SMS lands as adaptive cards in the channel. Channel-level routing lets you pipe production OTPs into one channel and dev signups into another.
Webhooks
For anything Slack and Teams don't cover. Subscribe your endpoint to events (inbound SMS, delivery, lifecycle), set a signing secret, and receive HMAC-SHA256-signed POST requests. The webhooks reference page covers the payload shapes, retry policy, and signature verification.
The lowest-friction option. Each number can forward to one or more email addresses; the message body, sender, and timestamp arrive in a clean template. Useful for fallback delivery when Slack/Teams aren't an option (contractors, external auditors, etc.).
SMS forwarding
Relay incoming SMS to another phone number. Plan-dependent — included in higher tiers, available as an add-on otherwise. The forwarded message is delivered from a SIMRelay-managed sender so the original carrier is preserved in the audit trail.
API
Everything above can also be wired through the API. If you'd rather skip the dashboard and provision numbers + configure routing programmatically (e.g., from your own onboarding flow), the API is the path. See the API reference.