Integrations
Receiving message statuses by webhook
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
An API response shows a job was created, not the final result. Your CRM needs a separate stream of status changes.
Build the solution
Configure a public HTTPS webhook. Verify the signature of the raw request body, persist the event, then acknowledge it. Update the order record by message ID and allow for repeated event delivery.
Check before launch
Do not verify against re-serialised JSON. Sent is not delivered. For unknown status, let a responsible person decide whether to send again.
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.
