Skip to content

How it works

SMSFabric sits between your code and your phones. Your code talks to the API over HTTPS. Your phones keep a secure connection open to SMSFabric and send each message through one of their SIMs.

  1. You send a request. Your server calls POST /v1/messages with an API key, or someone presses Send in the portal. SMSFabric checks the key, the recipients and the blacklist, stores the message encrypted and answers 201 Created with status queued.

  2. SMSFabric picks a phone and a SIM. The router chooses the device, SIM or pool you asked for, or your default SIM. It respects each SIM’s daily limit and the cooldown between messages. The status becomes routed.

  3. The phone sends it. The phone receives the job over its live connection. If the connection was asleep, a push notification wakes it first. The phone hands the message to Android, which sends it through the carrier. The status moves to sending, then sent.

  4. The carrier reports back. When the recipient’s handset receives the SMS, the carrier sends a delivery report to the phone, and the phone passes it on. The status becomes delivered, or failed with an error code.

  5. You hear about it. Each change is written to the message’s timeline, shown live in the portal and posted to your webhooks as message.sent, message.delivered or message.failed.

  1. queued
  2. routed
  3. sending
  4. sent
  5. deliveredfailedblocked
Every outbound message ends in one terminal status: delivered, failed or blocked.

A message to a blacklisted or opted-out number never leaves SMSFabric. It is stored with status blocked.

When someone texts one of your SIMs, the Android app (the direct build) reads the SMS and sends it to SMSFabric. It appears in Messages with direction inbound and status received, and SMSFabric posts a message.received webhook. If the text is STOP, the number is added to your blacklist. See Inbound SMS.

Phones report a heartbeat. If a phone stops reporting, the portal marks it offline and its waiting messages stay queued. When the phone is in a pool, SMSFabric moves those messages to another online phone in the same pool. When it is alone, they are sent as soon as it reconnects.

API keys that start with sf_test_ never reach a carrier. A virtual device accepts their messages and reports them as delivered, so you can build and test your integration before you pair a real phone. See Sandbox.