Core concepts
Organisation
Section titled “Organisation”Everything you create belongs to an organisation: phones, messages, contacts, keys and webhooks. People join an organisation by invitation, and one person can belong to several. Data never crosses between organisations.
Roles and permissions
Section titled “Roles and permissions”Each member has a role: owner, admin, developer, campaign_manager, agent, viewer or billing. A role is a set of permissions such as messages:send or devices:manage. See Team and roles for the full table.
Device
Section titled “Device”A device is an Android phone running the SMSFabric app and paired with your organisation. It sends and receives SMS through its SIMs. A device is online while it keeps reporting its heartbeat.
Each SIM (or eSIM) in a device is a sending channel with its own number, carrier, optional daily limit and label. One SIM in the organisation is the default sender. You can pick a SIM per message with simId.
A pool is a group of devices that share the work. Send with poolId and SMSFabric spreads messages across the pool’s online phones. If one fails or goes offline, its messages move to another phone in the pool.
Message
Section titled “Message”A message has a direction (outbound or inbound), a status and a timeline of events. Outbound statuses are queued, routed, sending, sent, then one final status: delivered, failed or blocked. Inbound messages have status received. Message bodies are encrypted at rest.
Segments and encoding
Section titled “Segments and encoding”Long texts travel as several SMS segments that the recipient’s phone joins back together. Messages that use only the GSM-7 alphabet fit 160 characters in one segment, or 153 per segment when split. Any other character, such as Arabic letters or emoji, switches the whole message to UCS-2: 70 characters in one segment, or 67 per segment when split. Your carrier usually charges per segment. A body can be up to 1,600 characters.
API key
Section titled “API key”An API key lets your server call the API. It has a mode, a set of scopes and optional limits:
- Live keys (
sf_live_…) send real SMS through your phones. - Test keys (
sf_test_…) go to a virtual device and never reach a carrier. - Scopes limit what the key can do. A key can only have permissions that its creator has.
- IP allowlist and expiry are optional extra limits.
The secret is shown once when you create the key. SMSFabric stores only a hash. See Authentication.
Webhook
Section titled “Webhook”A webhook is an HTTPS address of yours that SMSFabric calls when something happens, such as message.delivered or device.offline. Every call is signed so you can check it came from SMSFabric. See Webhooks.
Contacts, templates and campaigns
Section titled “Contacts, templates and campaigns”Contacts are the people you message, with tags, groups, custom fields and consent. Templates are reusable message bodies with variables such as {{firstName}}. A campaign sends a template to a set of contacts at a controlled rate, outside quiet hours. See Campaigns.
Verify
Section titled “Verify”Verify sends one-time codes by SMS and checks them, with limits that stop SMS pumping fraud. See Verify (OTP).