For developers

Engineering teams use SIMRelay for the things engineering teams do: signing up for SaaS tools to evaluate them, running CI flows that need a phone number, provisioning per-customer numbers from their own product. The API is built for this.

Evaluating SaaS with shared accounts

Most B2B tools require phone verification on signup. If three engineers need to evaluate the same tool, the traditional approach is "one of us signs up and shares the password" — which then breaks at the next 2FA prompt. With SIMRelay, the team has one hosted number, one shared account, and everyone can complete 2FA flows.

CI and provisioning flows

If your product onboards customers in a flow that involves a phone-verified account (e.g., you provision a downstream service for each customer), SIMRelay can be the verification primitive in your CI tests and your production onboarding. The API supports claim, verification-code retrieval, and release in a sequence your CI runner can execute deterministically.

Programmatic team management

Teams, members, and per-team integrations are all API-managed. You can mirror your internal team structure into SIMRelay without touching the dashboard — useful for organizations with frequent restructuring.

Webhooks for everything

Subscribe to inbound SMS, delivery events, lifecycle changes. Verify signatures, deduplicate by event ID, retry on failure with exponential backoff. The webhook contract is documented in the webhooks reference.

SDKs

The HTTP API is straightforward enough that most teams call it directly. We don't ship an opinionated SDK because there are too many languages and frameworks to support well; what we do maintain is a set of well-tested example clients in Python, TypeScript, and Go. They're starting points, not framework-level abstractions.