SMS Provider Settings

The gateway every SMS goes through — and a test send, so you can prove it works before anything depends on it.

Gateway

These come from your provider's API documentation. The service substitutes the placeholders below into every request it makes.

Provider name A label for your own reference — it is never sent anywhere.

Method Whichever verb the provider's send endpoint expects.

Send URL Placeholders, substituted and encoded for every send. %NAME% works too, and anything the service does not recognise is left exactly as you typed it, so a typo shows up in the reply rather than vanishing:

{API_KEY} {SENDER} {NUMBER} {MESSAGE}

A typical Bangladeshi gateway looks like this — copy the exact URL and parameter names from your own provider's docs, because every one of them differs:
https://sms.example-gateway.net/api/v3/sendsms?api_key={API_KEY}&type=text&senderid={SENDER}&number={NUMBER}&message={MESSAGE}

API key Stored by the service and never shown again.

API secret key A second credential a few gateways (e.g. REVE) need alongside the API key. Leave blank if yours uses a single key — it is stored by the service and never shown again.

Sender ID The name or short code recipients see. It must be one the provider approved.

Number format How a mobile number is rewritten before it goes into the request.

Extra headers (JSON, optional) Only if your provider needs headers as well as the URL — a JSON object of name/value pairs, and {API_KEY} works inside a value for token-style APIs. Leave blank otherwise.

What counts as sent

Bangladeshi gateways routinely answer 200 OK with an error in the body, so "the request worked" and "the SMS was accepted" are not the same fact. Tell the service how to tell them apart — the test send below shows you exactly what your gateway replies.

Success rule Start with HTTP status, run the test, then tighten it once you have seen a real reply.

Failure marker If the reply contains this text the message is recorded as failed even when the rule above says otherwise — this is what catches a 200 carrying {"error":"Invalid API key"}. Leave blank to switch the override off.

Limits and safety

Every SMS costs money, and a loop somewhere else in the platform must not be able to spend it. Leave a box blank to keep the value the service already holds.

Timeout (seconds) 1–30. How long to wait for the provider before recording a failure.

Max per minute 1–600. Sends beyond this are recorded as blocked, not sent.

Daily cap 1–100,000 messages per day, across the whole service.

Duplicate window (seconds) 0–3600. The same text to the same number inside this window is suppressed. 0 turns it off.

Gateway enabled — the service may send SMS through it Turn this off to stop every outgoing SMS without losing these settings.

Loading provider settings…

SMS Provider Settings

The SMS gateway is not connected yet

Gateway

What counts as sent

Limits and safety

Send test SMS