Custom HTTP gateway setup
Any provider with a REST API works. Paste the endpoint, set auth, map fields — done in 3 minutes. This is how 100+ gateways connect to Alintro.
1. Find your provider's send-SMS API docs
Every SMS API has a reference page like "Send an SMS" with:
- A URL endpoint (e.g.
https://api.provider.com/v1/send) - HTTP method (usually POST)
- Auth method (API key header, basic auth, or bearer token)
- Request body template (JSON or form-encoded)
- A success response format
2. Go to Notif app → Gateways → Add custom HTTP
Fill in the form:
Name
Pick anything — "FastSMS Primary" or "MyProvider Transactional".
Endpoint
Full URL from docs.
Method
Usually POST.
Headers
One key=value per line. Example:
Content-Type: application/json
Authorization: Bearer YOUR_API_KEYBody template
Use {{to}}, {{text}}, {{from}} as placeholders. Alintro fills these per-message. Example (JSON):
{
"to": "{{to}}",
"from": "{{from}}",
"text": "{{text}}",
"dlt_template_id": "1234567890123456789"
}Form-encoded is also supported — Alintro detects the Content-Type header.
Success matcher
A substring that tells Alintro the send succeeded. Examples:
"status":"success"(MSG91)"queued"(Twilio)"return_code":201
3. Test
Click Test connection. Alintro sends a test message to your admin phone. On failure, the raw HTTP response is shown so you can debug.
Template placeholders reference
The full list:
{{to}} — recipient E.164 number
{{from}} — configured sender
{{text}} — message body (rendered template)
{{dlt_template_id}} — India DLT template ID per-message
{{customer_name}} — order customer name
{{order_number}} — Shopify order #
{{tracking_number}} — shipment tracking
{{amount}} — order total
{{shop_name}} — store name
{{unsubscribe_url}} — opt-out link (compliance)See the full template variables reference for all 30+ placeholders.
Not sure which provider to pick?
Browse 120+ supported gateways, filtered by region and channel.
Browse all gateways