Integrations
Pairing a phone from your application
Implementation scenario · This is an example implementation, not a story about a named customer. Results depend on your integration, phone, network and carrier.
AI-generated scenario illustrationThe problem
Your CRM user wants to add a work phone without entering the SIM Bridge admin area. Pairing needs a one-time code, not a shared device secret.
Build the solution
Your project backend requests a pairing code through the API and shows it to an authorised user. The Android app receives the server address and code. After pairing, store deviceId in your business model.
Check before launch
The code lasts ten minutes and is single-use. Keep it out of logs. Check device limits and the requesting user’s permissions.
How SIM Bridge works
Your backend creates a job through the API, and the connected Android sends SMS through your SIM. Store the message ID in your system and receive status changes through a webhook. A queued job is not yet a sent message: the phone must be available and the carrier must accept it.
Start with your own test number. Check Android permissions, screen-off connectivity, retries with the same Idempotency-Key, and unknown-status handling. Keep API keys out of browser code and public repositories.
