Skip to main content

Enterprise SMS Gateways and Carrier Adapters

BrokerOS isolates external telecommunication protocols inside self-contained TypeScript packages within integrations/sms/. Neither apps/api nor apps/workers makes direct HTTP calls to SMS aggregators; all transmission, signature validation, and error normalization route through these typed adapters. Through the SMS Gateway Configuration Studio (SmsProviderConfigCard.tsx), administrators can connect and manage nine enterprise SMS services simultaneously.

Gateway Connection Architecture


The Nine Supported SMS Gateways

Twilio Programmable SMS

Global carrier aggregator. Connects via Account SID, Auth Token, and Messaging Service SID. Full 10DLC registration support and inbound webhooks.

Amazon SNS / Pinpoint

High-throughput cloud SMS relay. Connects via IAM Access Key ID, Secret Key, AWS Region, and Sender ID. Ideal for large-scale transactional broadcasts.

Gupshup Enterprise

Primary telecom aggregator for Indian real estate operations. Connects via User ID, Password, and TRAI DLT Header IDs.

Sinch

Tier-1 direct carrier connection network. Connects via Service Plan ID, API Token, and verified sender number.

Infobip

Enterprise cloud communications platform with direct mobile network operator (MNO) routes. Connects via API Key and Base URL.

Telnyx

Private global IP communications network with direct carrier peering. Connects via API Key and Messaging Profile ID.

Plivo

Carrier platform with high delivery rates across North America. Connects via Auth ID and Auth Token.

Vonage (Nexmo)

Global telecommunication API. Connects via API Key, API Secret, and Brand Sender ID.

Bird (MessageBird)

Omnichannel messaging network. Connects via Access Key and registered Originator ID.

Required Gateway Configuration Parameters


Regulatory Compliance Frameworks

BrokerOS simplifies navigation across global telecom regulations:

United States: A2P 10DLC Regulations

  • Requires registering your brokerage business brand and specific campaign use case (such as Customer Care & Marketing) with the Campaign Registry (TCR).
  • Assigns Trust Scores that determine maximum Messages Per Second (MPS) allowed on 10-digit local numbers.

India: TRAI DLT (Distributed Ledger Technology)

  • Enforces strict registration across the regulatory blockchain before any commercial SMS is delivered.
  • Every message must carry an approved Principal Entity ID (PE ID), Sender Header ID (6 characters, for example, SKYLNE), and pre-approved DLT Content Template ID.