Skip to content

Go live

Your integration works with an sf_test_ key. Going live means real SIMs, real recipients and real costs on your carrier plan. Work through this list before you switch.

  1. Pair at least two Android phones, so one can be offline without stopping your traffic (Pair a phone).
  2. Put them in a pool and send with poolId to get round robin and failover.
  3. Keep them on a charger, on Wi-Fi or with good signal, and exclude the app from battery optimization (Battery).
  4. Check each SIM’s plan: SMS allowance, daily limits from the carrier, and international sending if you need it. Set a dailyLimit per SIM with PATCH /v1/devices/:id/sims/:simId to stay under the carrier’s limits.
  5. Choose the default SIM with POST /v1/devices/:id/sims/:simId/default, or in Devices.
  1. Create a key with Live · real SMS as the Mode, and only the scopes the service needs (Authentication).
  2. Add an IP allowlist if your servers have fixed addresses, and an expiry if your rotation process allows it.
  3. Put the key in your secret manager as a new value, for example SMSFABRIC_API_KEY. Keep the test key for staging and CI.

Nothing else changes in your code: the base URL, request bodies and responses are the same.

Terminal window
# A live smoke test to your own number. Check that it arrives.
curl https://api.smsfabric.com/v1/messages \
-H "X-Api-Key: $SMSFABRIC_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: go-live-smoke-1" \
-d '{"to": "+201001234567", "body": "SMSFabric live test"}'
  • Every send has an Idempotency-Key derived from your own data (Idempotency).
  • Network errors, 429 and 5xx are retried with backoff; 4xx are not (Errors).
  • Your code handles blocked in the send response and failed later.
  • Your webhook endpoint verifies signatures on the raw body and deduplicates on SMSFabric-Event-Id (Webhooks).
  • The webhook endpoint answers within 10 seconds and is subscribed only to the events you use.
  • Phone numbers are stored and sent in E.164.
  • Logs don’t contain the API key, message bodies or full phone numbers.
  • Recipients agreed to receive your messages. Record it in each contact’s consent.
  • Marketing messages say how to opt out (“Reply STOP to opt out”). SMSFabric honours STOP and START automatically (Receive messages).
  • Your quiet hours and send window match local rules.
  • For OTPs, Verify countries are limited to the ones you serve.
  • Your SIMs’ terms allow the kind and volume of traffic you send.
  • Watch the portal’s Overview for failed messages and offline phones.
  • Subscribe to device.offline and alert someone when a phone drops out.
  • Review failed webhook deliveries in Developers → Webhooks, and replay them after an outage.
  • Check the audit log for key creation and role changes.
  • Rotate the API key on a schedule with POST /v1/api-keys/:id/rotate: the old secret keeps working for 24 hours while you deploy the new one.