Integration Guides · 3 min read · Nov 05, 2026

How to Migrate from Notify to SwiftInbox SMS: Simple Integration & API Guide

A simple step-by-step guide to migrating your SMS setup from standalone Notify to SwiftInbox. Sync your approved DLT templates in one click, unify your wallet, and update your API calls in under 5 minutes.

AR
Swift Inbox Team
Product & Integrations
Helps teams build reliable WhatsApp and SMS messaging workflows with clean APIs and unified billing.
Share:
How to Migrate from Notify to SwiftInbox SMS: Simple Integration & API Guide
⚡

Too Long? Read This in 10 Seconds

Executive bullet points for fast decision-making

  • ✓ Stop juggling two separate dashboards: SwiftInbox brings WhatsApp and SMS into one unified workspace.
  • ✓ Keep your existing DLT approvals: Your registered Entity ID, Sender IDs (Headers), and Template IDs remain 100% compliant.
  • ✓ One shared wallet: One balance pays for Meta WhatsApp conversations and telecom SMS dispatches with automated ledger receipts.
  • ✓ 1-click template sync: Pull all approved Notify templates and headers directly into your SwiftInbox workspace.
  • ✓ Modern REST API: Replace legacy URL parameter strings with clean JSON requests (POST /api/v1/sms/send) using Bearer tokens.

If your team is managing WhatsApp marketing on one portal and logging into Notify (notify.appringer.co.in) for transactional SMS, you are dealing with two separate balances, disconnected customer lists, and split analytics.

With SwiftInbox SMS, you can run both channels from a single dashboard. Your telecom routes, approved DLT Sender IDs, and templates remain untouched—while your team gains a unified wallet, live delivery telemetry, and a clean developer API.

Here is the straightforward 5-minute migration guide.


What Changes After Migrating?#

Feature Old Notify Setup SwiftInbox SMS
Logins & Dashboards Separate portal for SMS Unified workspace (WhatsApp + SMS)
Billing & Wallet Separate SMS recharge 1 Shared Wallet for WhatsApp & SMS
DLT Templates Manual copy-pasting 1-Click Sync directly into workspace
Campaign Retries Manual CSV export / import 1-Click SMS Fallback for failed WhatsApp recipients
API Format Query parameters in GET/POST URLs Standard REST API (JSON) with Bearer tokens
Phone Book & CRM Disjointed recipient list Centralized contacts with tags, custom fields & history

Step 1: Generate Your SwiftInbox API Key#

To send SMS from your CRM, website, or backend applications, create a secure API token:

  1. Log in to your SwiftInbox Dashboard.
  2. Go to Manage → Settings → Integrations & API Keys (or /settings/integrations).
  3. Click Create API Key.
  4. Give it a descriptive name (e.g., Production CRM SMS) and check the sms:send permission.
  5. Copy the generated Bearer Token (starts with swft_...).

Step 2: Sync Your DLT Templates in 1 Click#

You do not need to re-register your templates or re-apply for DLT approvals.

  1. In SwiftInbox, open the Manage menu and click SMS Templates (/sms-templates).
  2. Click the "Sync from Notify" button in the top right.
  3. SwiftInbox automatically fetches all your approved DLT Sender IDs (e.g., APPRNG) and Content Template IDs (1707...).
  4. Test Delivery: Click "Quick Test" next to any synced template, enter your mobile number, fill sample variables, and verify that the SMS delivers immediately to your phone.

Step 3: Update Your Backend API Call#

Replacing your legacy Notify API calls with SwiftInbox takes less than 2 minutes.

Side-by-Side Comparison#

Old Notify Call (Query Parameters):

GET https://notify.appringer.co.in/cpaas/sms?username=your_user&password=your_pass&senderid=APPRNG&mobile=9876543210&message=Your+OTP+is+123456&dlt_template_id=1707161234567890123

New SwiftInbox Call (Clean REST JSON):

POST https://swiftinbox.in/api/v1/sms/send
Authorization: Bearer swft_your_api_token_here
Content-Type: application/json

{
  "to": "+919876543210",
  "message": "Your OTP is 123456. Valid for 10 minutes. - AppRinger",
  "sender_id": "APPRNG",
  "dlt_template_id": "1707161234567890123"
}

Code Examples#

Here are copy-paste snippets for your tech stack:

cURL#

curl -X POST https://swiftinbox.in/api/v1/sms/send \
  -H "Authorization: Bearer swft_your_api_token_here" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+919876543210",
    "message": "Your verification code is 482910. Valid for 10 mins. - AppRinger",
    "sender_id": "APPRNG",
    "dlt_template_id": "1707161234567890123"
  }'

PHP (cURL)#

<?php

$payload = [
    'to'              => '+919876543210',
    'message'         => 'Your verification code is 482910. Valid for 10 mins. - AppRinger',
    'sender_id'       => 'APPRNG',
    'dlt_template_id' => '1707161234567890123',
];

$ch = curl_init('https://swiftinbox.in/api/v1/sms/send');
curl_setopt_array($ch, [
    CURLOPT_POST           => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER     => [
        'Authorization: Bearer swft_your_api_token_here',
        'Content-Type: application/json',
        'Accept: application/json',
    ],
    CURLOPT_POSTFIELDS     => json_encode($payload),
]);

$response = curl_exec($ch);
curl_close($ch);

$result = json_decode($response, true);
echo "Message ID: " . $result['data']['id'];

Node.js (Fetch)#

const response = await fetch('https://swiftinbox.in/api/v1/sms/send', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer swft_your_api_token_here',
    'Content-Type': 'application/json',
    'Accept': 'application/json'
  },
  body: JSON.stringify({
    to: '+919876543210',
    message: 'Your verification code is 482910. Valid for 10 mins. - AppRinger',
    sender_id: 'APPRNG',
    dlt_template_id: '1707161234567890123'
  })
});

const data = await response.json();
console.log('Status:', data.data.status); // "sent" or "queued"

Python (Requests)#

import requests

url = "https://swiftinbox.in/api/v1/sms/send"
headers = {
    "Authorization": "Bearer swft_your_api_token_here",
    "Content-Type": "application/json",
    "Accept": "application/json"
}
payload = {
    "to": "+919876543210",
    "message": "Your verification code is 482910. Valid for 10 mins. - AppRinger",
    "sender_id": "APPRNG",
    "dlt_template_id": "1707161234567890123"
}

response = requests.post(url, json=payload, headers=headers)
print(response.json())

Step 4: Sending Bulk SMS via API (Optional)#

If your system sends automated batches (e.g., daily order updates, appointment reminders), use the bulk endpoint to send up to 500 messages in a single HTTP request:

curl -X POST https://swiftinbox.in/api/v1/sms/bulk \
  -H "Authorization: Bearer swft_your_api_token_here" \
  -H "Content-Type: application/json" \
  -d '{
    "messages": [
      {
        "to": "+919876543210",
        "message": "Hi Rahul, your order #1024 is out for delivery. - AppRinger",
        "sender_id": "APPRNG",
        "dlt_template_id": "1707161234567890123"
      },
      {
        "to": "+919876543211",
        "message": "Hi Priya, your order #1025 is out for delivery. - AppRinger",
        "sender_id": "APPRNG",
        "dlt_template_id": "1707161234567890123"
      }
    ]
  }'

Step 5: Checking Delivery Status (DLR)#

SwiftInbox reconciles telecom delivery receipts automatically. You can check the status of any sent message via API:

curl -X GET https://swiftinbox.in/api/v1/sms/{id} \
  -H "Authorization: Bearer swft_your_api_token_here"

Response Example:

{
  "success": true,
  "data": {
    "id": 14205,
    "uuid": "sms_9b4e12e8-581f-4b08-8e6f-442898dbf142",
    "to": "+919876543210",
    "status": "delivered",
    "sender_id": "APPRNG",
    "segments": 1,
    "billed_amount": "0.1800",
    "sent_at": "2026-11-05 14:15:20",
    "delivered_at": "2026-11-05 14:15:24"
  }
}

If your application needs instant push notifications when an SMS is delivered, you can configure your webhook endpoint in Manage → Settings → Developer Webhooks.


Step 6: Quick SMS Directly from the Dashboard#

For non-developers, sending a one-off SMS is as simple as clicking a button:

  1. Open your Phone book (/contacts).
  2. Search for any contact.
  3. Click the blue "SMS" button in the actions column.
  4. Select a template, enter the variable values, and click Send. The wallet is automatically debited, and the message history appears in real time.

Need Help Migrating?#

Our support team can help you sync your Notify templates, test your API scripts, and verify your DLT headers:

  • WhatsApp Support: Reach out directly through the live chat widget on your dashboard.
  • Email: support@swiftinbox.in
  • API Documentation: Visit /docs/api inside your workspace for full endpoint specs and schema references.

Frequently asked questions

Will migrating disrupt my approved DLT templates or Sender IDs? +

No. Your DLT registration with telecom operators (Airtel, Jio, Smartping, Vilpower) stays exactly as is. SwiftInbox routes through your approved headers with zero re-registration needed.

Do I need separate prepaid balances for WhatsApp and SMS? +

No. SwiftInbox uses a single unified prepaid wallet. One recharge pays for WhatsApp Cloud API conversations and SMS dispatches.

Can I send SMS campaigns to failed WhatsApp audiences? +

Yes. If a WhatsApp campaign has failed or unreachable recipients, you can click 'Retarget Failed' to launch an instant SMS fallback campaign in one click.

What is the difference between single SMS and bulk SMS? +

Use /api/v1/sms/send for immediate single alerts (OTPs, notifications) and /api/v1/sms/bulk to send up to 500 personalized messages in a single API call.

Related Articles