Your SMS are sent from your own mobile.See how it works
SMSMobileAPISMSMobileAPIMobile infrastructure, connected
DashboardCreate free account
PLATFORMAPI-first architectureSecure device pairingDelivery visibilityMulti-device controlVersioned documentation
← All integrations
External SMS Gateway + SMSMobileAPI

OPTIONAL SMS DELIVERY ROUTES

Connect your
external SMS infrastructure.

Add a supported SMS provider, a private HTTP service or a physical gateway to SMSMobileAPI. Keep your mobile-powered gateway available while managing additional SMS senders from the same workspace.

Connect a serviceSee how it works
Multiple routesMobile, provider or private gateway Account scopedConnections belong to your account Dedicated keyOne secondary API key per connection
SMS routing workspaceREADY
API
SMS REQUESTRecipient + message

Authenticated SMSMobileAPI workflow

NEW
select sender
CONTROL LAYERSMSMobileAPIAccount access + sender selection + activity
01Connected mobileYour SIM and number
02SMS providerSupported vendor account
03Private gatewayHTTP or physical system
SELECTED ROUTE

Message sent through Warehouse Gateway.

Accepted ✓
You choose an available connection. SMSMobileAPI routes the SMS through that configured sender.

ONE WORKSPACE, SEVERAL SMS OPTIONS

Keep the native mobile gateway. Add another route when it makes sense.

The official SMSMobileAPI mobile application remains the simplest way to send through your own phone and number. External SMS connections extend that setup when a workflow requires another provider, a dedicated sending account or private infrastructure.

  • Continue sending through a connected mobile and its existing SIM.
  • Add a supported external SMS provider account.
  • Map a private HTTP, physical or GoIP-style gateway.
  • Select only connections that are linked to your SMSMobileAPI account.
01NATIVE

Your connected mobile

Send SMS through the official application, your phone, your SIM and your existing number.

The core SMSMobileAPI experience.
02EXTERNAL

Provider or private gateway

Connect another SMS account or map your own sending infrastructure when an additional route is required.

Optional and dedicated to SMS delivery.

CONNECT, TEST, THEN USE

Four controlled steps to add an SMS sender.

The dashboard adapts the connection form to the route you choose and keeps every external sender attached to the correct account.

  1. 01
    ⌁

    Choose the route

    Select a supported provider or choose the personal gateway configuration.

  2. 02
    ◇

    Add connection data

    Enter the provider credentials or the private HTTP parameter mapping.

  3. 03
    ✓

    Save the connection

    SMSMobileAPI creates an account-scoped connection and a secondary API key.

  4. 04
    →

    Send a test SMS

    Select the new sender in the SMS screen and validate it with controlled data.

TWO WAYS TO CONNECT

Use a catalog provider or your own gateway.

The available provider catalog is managed from the live dashboard. If your infrastructure is not listed, the personal gateway option can map a compatible HTTP sending URL.

SUPPORTED PROVIDER01

Connect an existing SMS provider account.

Choose an available provider and enter the fields requested by its production definition. Add a recognizable connection reference, then save.

  • Provider-specific form
  • Masked credentials in the dashboard
  • Dedicated secondary API key
  • Connection can be removed when credentials change
Browse available providers
PERSONAL GATEWAY02

Map a private HTTP or physical gateway.

Provide the base sending URL and identify the parameters used for the recipient and message. Fixed gateway parameters can remain in the configured base URL.

REQUEST MAPPINGhttps://gateway.example/send
?to={recipient}&text={message}
Connect my own gateway

HYBRID SMS INFRASTRUCTURE

Bring an existing delivery system into your SMSMobileAPI stack.

External gateways are useful when a company already operates a provider account, specialist route, private HTTP service or physical SMS hardware. SMSMobileAPI adds a common control point without removing the connected-mobile option.

IMPORTANT DISTINCTION

An external connection is an optional SMS sender. It does not send WhatsApp messages and does not automatically replace a failed route unless your own workflow implements that decision.

Clear routing, without hidden assumptions
Open External SMS Service
Mobile phone, SMSMobileAPI control layer and external SMS infrastructure connected together
Combine the mobile gateway with an external SMS route when your operation requires it.

SELECT THE RIGHT SENDER

Connected routes appear where sender selection is supported.

Use a connected mobile, an external SMS service or a personal gateway from compatible SMSMobileAPI screens. Each external connection has a recognizable name or reference so the operator knows which route is being used.

Manage connectionsSend a test SMS
Send from3 AVAILABLE
Only senders linked to this account are displayed.

CONNECTION SECURITY

Separate the external route from your main account key.

Provider credentials are stored server-side and displayed in masked form. SMSMobileAPI generates a dedicated secondary API key for each connection, so the main account API key does not need to be shared with the external route.

  • 01
    Dedicated secondary keyA separate key identifies the external connection.
  • 02
    Masked credentialsSensitive provider values are not shown openly in listings.
  • 03
    Account ownership checksA sender must belong to the authenticated SMSMobileAPI account.
  • 04
    Removable connectionDelete and recreate a provider connection when credentials change.

WHEN AN EXTERNAL ROUTE HELPS

Built for existing infrastructure and specific delivery needs.

↔

Hybrid operations

Keep mobile sending while adding a provider or private gateway for selected workflows.

▦

Existing hardware

Connect compatible physical or GoIP-style infrastructure instead of replacing it.

◎

Specialist routes

Use an existing provider account when a region or business process requires it.

✓

Controlled migration

Introduce SMSMobileAPI while retaining an established delivery route during transition.

EXTERNAL SMS GATEWAY FAQ

Understand what the connection does.

An external gateway expands the available SMS sending routes. It does not replace the native mobile gateway or change how WhatsApp is connected.

Do I have to stop using my connected mobile?

No. The mobile-powered gateway remains available. An external service or personal gateway is an additional SMS sender that can be selected where the workflow supports sender selection.

Can I connect my own physical or HTTP gateway?

Yes, when it offers a compatible HTTP sending URL. Configure the base URL plus the parameter names used for the recipient and message.

Are external provider charges included?

No. Provider, carrier, server and hardware costs remain governed by the external service or infrastructure you connect.

Does this create automatic fallback routing?

No automatic failover is promised by this connection alone. Your workflow must explicitly select or implement the route decision it requires.

Can an external SMS connection send WhatsApp?

No. External SMS service connections are dedicated to SMS. Use the separate WhatsApp connection and sender configuration for WhatsApp delivery.

YOUR INFRASTRUCTURE, ONE CONTROL POINT.

Connect the SMS route your operation already uses.

Keep your connected mobile, add a supported provider or map a private gateway, then validate the complete path with a controlled SMS test.