Send SMS via API — Integrate in Minutes | Techto Networks
- TechTo Networks
- Jul 2, 2025
- 18 min read
Updated: May 12
99.9% Uptime SLA. DLT-Compliant. Live in Under 5 Minutes. Your first SMS delivered in minutes — not days. TechTo's Send SMS API gives you enterprise-grade messaging infrastructure, India's fastest DLT compliance engine, and a one-click sandbox — all without a setup fee.
Why 5,000+ Businesses Choose TechTo's Send SMS API
When you're ready to integrate, you need a send SMS API that delivers on every front — speed, reliability, compliance, and developer experience. TechTo Networks was built from the ground up to solve the exact problems that slow teams down: DLT registration headaches, unpredictable delivery, opaque pricing, and poor developer tooling.
Here's what you get from the moment you sign up:
Sub-second delivery across all Indian carriers and 180+ countries globally. Fully automated DLT compliance — register sender IDs and templates without leaving the TechTo dashboard. 99.9% uptime SLA backed by a multi-carrier failover architecture — if one route fails, your message routes instantly to a backup. Sandbox environment available on signup — test without spending a rupee or sending a real message. Pay only for what you send — no monthly minimums, no hidden fees, no lock-in.
Get Your First SMS Out in Under 5 Minutes
Most SMS API providers have you jumping through portals, waiting for approvals, and reading 80-page docs before you send a single test message. TechTo is different.
Step 1 — Sign up (60 seconds) Create your free account at techtonetworks.com/register. No credit card required.
Step 2 — Get your API key (instant) Your API key is generated automatically on account creation. Find it under Dashboard → Developer → API Keys.
Step 3 — Hit the sandbox (zero cost) Every account includes a fully-featured sandbox environment. Send test messages to virtual numbers, simulate delivery failures, and test webhook responses — all without touching production.
Step 4 — Make your first real API call Copy the code below. Replace the key. Run it. Your message lands on a real phone within seconds.
Step 5 — Go live Switch sandbox: true to sandbox: false in your payload. That's it. You're in production.
Send Your First SMS — Code in 6 Languages
cURL
bash
curl -X POST https://api.techtonetworks.com/v1/messages \
-H "Authorization: Bearer $TECHTO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"to": "+919876543210",
"from": "TECHTO",
"body": "Your OTP is 847203. Valid for 10 minutes. — TechTo",
"sandbox": false
}'Python
python
import requests, os
def send_sms(to, body, sender="TECHTO"):
response = requests.post(
"https://api.techtonetworks.com/v1/messages",
json={"to": to, "from": sender, "body": body, "sandbox": False},
headers={
"Authorization": f"Bearer {os.environ['TECHTO_API_KEY']}",
"Content-Type": "application/json"
}
)
data = response.json()
if response.ok:
print(f"✓ Sent | ID: {data['message_id']} | Status: {data['status']}")
else:
print(f"✗ Failed [{response.status_code}]: {data.get('message')}")
return data
send_sms("+919876543210", "Your OTP is 847203. Valid for 10 minutes.")Node.js
javascript
const axios = require('axios');
async function sendSMS(to, body, from = 'TECHTO') {
try {
const { data } = await axios.post(
'https://api.techtonetworks.com/v1/messages',
{ to, from, body, sandbox: false },
{ headers: { 'Authorization': `Bearer ${process.env.TECHTO_API_KEY}` } }
);
console.log(`✓ Message queued | ID: ${data.message_id}`);
return data;
} catch (err) {
console.error(`✗ Error: ${err.response?.data?.message || err.message}`);
throw err;
}
}
sendSMS('+919876543210', 'Your OTP is 847203. Valid for 10 minutes.');PHP
php
<?php
function sendSMS(string $to, string $body, string $from = 'TECHTO'): array {
$ch = curl_init('https://api.techtonetworks.com/v1/messages');
curl_setopt_array($ch, [
CURLOPT_POST => true,
CURLOPT_RETURNTRANSFER => true,
CURLOPT_POSTFIELDS => json_encode([
'to' => $to, 'from' => $from, 'body' => $body, 'sandbox' => false
]),
CURLOPT_HTTPHEADER => [
'Authorization: Bearer ' . getenv('TECHTO_API_KEY'),
'Content-Type: application/json'
]
]);
$result = json_decode(curl_exec($ch), true);
curl_close($ch);
return $result;
}
$result = sendSMS('+919876543210', 'Your OTP is 847203. Valid for 10 minutes.');
echo "Message ID: " . $result['message_id'];
?>Java
java
import java.net.http.*;
import java.net.URI;
public class TechToSMS {
static final String API_KEY = System.getenv("TECHTO_API_KEY");
static final String BASE_URL = "https://api.techtonetworks.com/v1/messages";
public static void main(String[] args) throws Exception {
String body = """
{"to":"+919876543210","from":"TECHTO",
"body":"Your OTP is 847203. Valid for 10 minutes.","sandbox":false}
""";
HttpRequest request = HttpRequest.newBuilder()
.uri(URI.create(BASE_URL))
.header("Authorization", "Bearer " + API_KEY)
.header("Content-Type", "application/json")
.POST(HttpRequest.BodyPublishers.ofString(body))
.build();
HttpResponse<String> response = HttpClient.newHttpClient()
.send(request, HttpResponse.BodyHandlers.ofString());
System.out.println(response.body());
}
}Go
go
package main
import (
"bytes"
"encoding/json"
"fmt"
"net/http"
"os"
)
func sendSMS(to, body, from string) error {
payload := map[string]interface{}{
"to": to, "from": from, "body": body, "sandbox": false,
}
jsonData, _ := json.Marshal(payload)
req, _ := http.NewRequest("POST",
"https://api.techtonetworks.com/v1/messages",
bytes.NewBuffer(jsonData))
req.Header.Set("Authorization", "Bearer "+os.Getenv("TECHTO_API_KEY"))
req.Header.Set("Content-Type", "application/json")
resp, err := http.DefaultClient.Do(req)
if err != nil { return err }
defer resp.Body.Close()
fmt.Printf("Status: %d\n", resp.StatusCode)
return nil
}
func main() {
sendSMS("+919876543210", "Your OTP is 847203. Valid for 10 minutes.", "TECHTO")
}API Reference — Core Endpoints
Send a Single Message
Request Parameters
Parameter | Type | Required | Description |
to | string | Yes | Recipient number in E.164 format (+919876543210) |
from | string | Yes | DLT-registered sender ID or virtual number |
body | string | Yes | Message text (160 chars GSM-7, 70 chars Unicode) |
sandbox | boolean | No | true for test mode; false (default) for production |
template_id | string | Conditional | Required for DLT-registered templates (India) |
send_at | string | No | ISO 8601 UTC timestamp for scheduled delivery |
callback_url | string | No | Webhook URL for delivery receipt push |
unicode | boolean | No | Force Unicode encoding for regional scripts |
Success Response (200 OK)
json
{
"message_id": "msg_9f3b12ac4d",
"status": "queued",
"to": "+919876543210",
"from": "TECHTO",
"segments": 1,
"encoding": "GSM-7",
"network": "Airtel India",
"cost": 0.0018,
"currency": "INR",
"created_at": "2025-07-03T10:00:00Z"
}Send Bulk Messages (Batch)
json
{
"from": "TECHTO",
"template_id": "tmpl_abc123",
"messages": [
{ "to": "+919876543210", "variables": { "name": "Rahul", "otp": "847203" } },
{ "to": "+919876543211", "variables": { "name": "Priya", "otp": "192847" } },
{ "to": "+919876543212", "variables": { "name": "Arjun", "otp": "374958" } }
]
}Check Message Status
Get Account Balance
List Registered Templates (India DLT)
Error Response Format
json
{
"error": "invalid_phone_number",
"message": "The 'to' field must be a valid E.164 formatted phone number.",
"code": 422,
"docs": "https://docs.techtonetworks.com/errors/422"
}HTTP Status Code Reference
Code | Meaning | Resolution |
200 | Message queued | Log message_id, set up webhook for DLR |
400 | Bad request | Review required fields and data types |
401 | Invalid API key | Regenerate key in Dashboard → Developer |
403 | Forbidden | IP not in allowlist or account suspended |
422 | Validation error | Fix phone format (E.164) or template mismatch |
429 | Rate limit hit | Implement exponential backoff |
500 | Internal error | Retry with backoff; check status.techtonetworks.com |
Pricing — Transparent, No Surprises {#pricing}
TechTo operates on a pay-as-you-go model with volume discounts at every tier. No monthly minimums. No setup fees. No exit penalties.
Starter — Free to Start
₹0/month — Best for developers, prototypes, and testing
100 free SMS credits on signup (no card needed)
Full API access (sandbox + production)
Up to 10 SMS/second throughput
Standard delivery routing
Email support
99.5% uptime SLA
Growth — For Scaling Teams
Pay per SMS — Best for startups and growing businesses
₹0.18 per SMS (domestic India, Transactional)
₹0.12 per SMS (promotional, DLT-compliant)
Up to 100 SMS/second throughput
Failover routing across 3 carrier routes
Webhook delivery receipts
DLT template management console
Priority email + chat support (business hours)
99.9% uptime SLA
Enterprise — For High-Volume Operations
Custom pricing — Best for banks, aggregators, large enterprises
Volume pricing from ₹0.09/SMS at 10M+ messages/month
Unlimited throughput (SMPP + HTTP)
Dedicated carrier connections
Custom sender ID registration
Private SMPP cluster option
24/7 dedicated technical account manager
SLA-backed delivery guarantee
Custom DLT integration and template bulk upload
99.99% uptime SLA with credit-back guarantee
On-premise deployment option
All plans include: Real-time delivery reports, Unicode support, 180+ country coverage, REST API + Webhooks, Postman collection, API documentation, and GDPR-compliant data handling.
99.9% Uptime SLA — What It Actually Means
A lot of SMS providers advertise uptime. TechTo backs it with architecture.
Multi-Carrier Failover Routing
Every message sent through TechTo's API is automatically routed through our intelligent failover engine. If the primary carrier route is unavailable, degraded, or experiencing latency spikes, the message is rerouted to a secondary carrier within milliseconds — without any action required on your part.
How it works:
Message enters TechTo's ingestion layer.
Our routing engine queries real-time carrier health scores (updated every 15 seconds).
Message is assigned to the highest-quality route for that destination number's network.
If a delivery failure is detected, the message is automatically rerouted to Carrier Route 2, then Route 3.
Final DLR (Delivery Receipt) is pushed to your webhook once confirmed by the carrier.
Geo-Redundant Infrastructure
TechTo's API infrastructure runs across 3 geographically distributed data centers with automatic failover. A regional outage in one zone does not affect your message delivery.
Real-Time Status Page
Monitor TechTo's live system health at status.techtonetworks.com — including per-carrier delivery latency, API response times, and incident history.
SLA Credit-Back Policy (Enterprise)
Enterprise accounts receive credit-back guarantees for downtime events exceeding SLA thresholds:
Downtime Percentage | Credit |
99.9% – 99.5% uptime | 10% of monthly spend |
Below 99.5% uptime | 25% of monthly spend |
Below 99.0% uptime | 50% of monthly spend |
DLT Compliance Built Into the API — Not an Afterthought
India's TRAI DLT mandate is one of the most complex SMS compliance requirements in the world. Most providers expect you to handle it yourself. TechTo handles it for you — directly inside the platform.
What Is DLT Compliance?
The Distributed Ledger Technology (DLT) framework, mandated by TRAI, requires every commercial SMS sender in India to:
Register their business entity on the DLT platform with a verified PE (Principal Entity) ID.
Register every Sender ID (Header) — the alphanumeric name shown to recipients.
Register every message template with exact content, variable placeholders marked as {#var#}, and an approved category:
Transactional — OTPs, account alerts, booking confirmations
Service Implicit — Service notifications to existing customers
Service Explicit — Opt-in based service notifications
Promotional — Marketing and offers
Submit messages only through approved templates with matching sender IDs.
Unregistered sender IDs or templates are blocked at the carrier level before delivery — your messages simply vanish.
How TechTo Handles DLT for You
DLT Registration Assistance: TechTo's compliance team helps you complete DLT registration on supported telco portals, including Videocon (Vi), Airtel, Jio, BSNL, and TATA.
Sender ID Registration Console: Register, track, and manage all your sender IDs from one unified dashboard. Status updates (Pending → Approved) are reflected in real time.
Template Manager: Create, submit, and version-control your message templates directly in the TechTo dashboard. Paste your message text, define variable fields, select the category, and submit — TechTo routes it to the appropriate DLT portal automatically.
Template Validation at Send Time: When you pass a template_id in your API call, TechTo validates that the template is approved, the sender ID matches, and the message body conforms — before the message leaves the platform. DLT-violating messages are rejected at the API level with a clear error code and explanation.
Template Variable Binding: Pass dynamic values (customer name, OTP, amount) as variables in your API payload. TechTo automatically binds them into the approved template, replacing {#var#} placeholders before dispatch.
json
{
"from": "TECHTO",
"template_id": "tmpl_txn_otp_001",
"to": "+919876543210",
"variables": {
"otp": "847203",
"validity": "10 minutes"
}
}Automated DND Filtering: TechTo automatically checks recipient numbers against the TRAI DND (Do Not Disturb) registry for promotional messages. DND-registered numbers are filtered before dispatch — keeping your account compliant and your delivery rates accurate.
Security Architecture — Enterprise-Grade by Default
TechTo's send SMS API is built for production environments where security is non-negotiable.
Transport Security
All API communication runs over TLS 1.3 (with TLS 1.2 minimum). Deprecated SSL/TLS versions are blocked at the gateway level.
Authentication
Bearer token authentication via long-lived API keys (2,048-bit entropy). Keys are hashed at rest using bcrypt — even TechTo employees cannot read your raw API key.
For high-security environments, TechTo supports dual-key authentication with a primary key and a signing secret used for HMAC-SHA256 request signature verification.
IP Allowlisting
Lock your API key to specific IP addresses or CIDR ranges. Any request originating outside the allowlist is rejected with a 403 error before any processing occurs.
Webhook Signature Verification
Every delivery receipt webhook sent by TechTo includes an X-TechTo-Signature header — an HMAC-SHA256 hash of the payload signed with your account's webhook secret. Verify this on your server to ensure the payload is genuine.
python
import hmac, hashlib
def verify_webhook(payload: bytes, signature: str, secret: str) -> bool:
expected = hmac.new(
secret.encode(), payload, hashlib.sha256
).hexdigest()
return hmac.compare_digest(expected, signature)Data Privacy and Compliance
GDPR compliant — message payloads are processed in-transit and not persisted beyond configurable retention windows (default: 30 days, configurable down to 0).
ISO 27001 certified information security management.
PCI-DSS compliant for financial services customers.
SOC 2 Type II audit report available under NDA for enterprise customers.
Data residency options available for EU and India-regulated workloads.
Real-Time Webhooks and Delivery Receipts
Knowing a message was sent is not enough. Knowing it was delivered is what matters.
Delivery Receipt (DLR) Events
TechTo pushes real-time status events to your registered webhook URL. Configure it in the dashboard or per-request using the callback_url parameter.
Event types:
Event | Meaning |
message.queued | Accepted by TechTo API |
message.dispatched | Sent to carrier network |
message.delivered | Confirmed delivery to handset |
message.failed | Delivery failed (with reason code) |
message.expired | Message expired before delivery (e.g. phone off >48h) |
message.inbound | Recipient replied (two-way messaging) |
Sample DLR webhook payload:
json
{
"event": "message.delivered",
"message_id": "msg_9f3b12ac4d",
"to": "+919876543210",
"from": "TECHTO",
"status": "delivered",
"network": "Airtel India",
"segments": 1,
"latency_ms": 1243,
"delivered_at": "2025-07-03T10:00:01.243Z",
"cost": 0.0018,
"currency": "INR"
}Express.js Webhook Handler
javascript
const express = require('express');
const crypto = require('crypto');
const app = express();
app.use(express.raw({ type: 'application/json' }));
app.post('/webhooks/techto', (req, res) => {
// Verify signature first
const sig = req.headers['x-techto-signature'];
const expected = crypto
.createHmac('sha256', process.env.TECHTO_WEBHOOK_SECRET)
.update(req.body)
.digest('hex');
if (!crypto.timingSafeEqual(Buffer.from(sig), Buffer.from(expected))) {
return res.status(401).json({ error: 'Invalid signature' });
}
const event = JSON.parse(req.body);
switch (event.event) {
case 'message.delivered':
console.log(`✓ Delivered: ${event.message_id} in ${event.latency_ms}ms`);
// db.updateStatus(event.message_id, 'delivered');
break;
case 'message.failed':
console.log(`✗ Failed: ${event.message_id} — ${event.failure_reason}`);
// alertingService.notify(event);
break;
case 'message.inbound':
console.log(`← Reply from ${event.from}: ${event.body}`);
// handleInbound(event);
break;
}
res.status(200).json({ received: true }); // Respond fast, always 200
});Sending Bulk SMS via API — At Any Scale
Whether you're sending 500 appointment reminders or 5 million promotional messages, TechTo's bulk infrastructure scales without code changes on your side.
Batch API (Up to 10,000 Messages Per Call)
python
import requests, os
batch_payload = {
"from": "TECHTO",
"template_id": "tmpl_promo_festive_001",
"messages": [
{"to": "+919876543210", "variables": {"name": "Rahul", "discount": "25%"}},
{"to": "+919876543211", "variables": {"name": "Priya", "discount": "30%"}},
# ... up to 10,000 entries per request
]
}
response = requests.post(
"https://api.techtonetworks.com/v1/messages/batch",
json=batch_payload,
headers={"Authorization": f"Bearer {os.environ['TECHTO_API_KEY']}"}
)
result = response.json()
print(f"Batch ID: {result['batch_id']}")
print(f"Queued: {result['queued']} | Failed: {result['failed']}")Throughput by Plan
Plan | Max SMS/second | Max Batch Size | Concurrent Connections |
Starter | 10/sec | 1,000 | 2 |
Growth | 100/sec | 10,000 | 10 |
Enterprise | Unlimited | 100,000 | Custom |
SMPP (Enterprise) | 1,000+/sec | N/A | Custom |
Schedule for Later
json
{
"from": "TECHTO",
"to": "+919876543210",
"body": "Your appointment is tomorrow at 10:00 AM. Reply CONFIRM or CANCEL.",
"send_at": "2025-07-04T04:30:00Z"
}Messages scheduled in the future can be cancelled anytime before dispatch via:
Rate Limiting and Backoff
TechTo enforces per-second and per-minute rate limits by plan tier. When you exceed them, the API returns 429 Too Many Requests with a Retry-After header.
python
import time, requests
def send_with_backoff(payload, headers, max_retries=5):
for attempt in range(max_retries):
response = requests.post(
"https://api.techtonetworks.com/v1/messages",
json=payload, headers=headers
)
if response.status_code == 429:
wait = int(response.headers.get('Retry-After', 2 ** attempt))
print(f"Rate limited. Waiting {wait}s before retry {attempt + 1}...")
time.sleep(wait)
continue
return response
raise Exception("Max retries exceeded")Two-Way SMS — Receive Replies via API
TechTo's send SMS API supports full two-way messaging on virtual numbers and short codes. Customers can reply to your messages and your application receives those replies in real time via webhook.
Common two-way use cases:
Appointment confirmation (Reply CONFIRM/CANCEL)
Customer support initiation (Reply HELP to speak to an agent)
Survey responses (Reply 1 for Yes, 2 for No)
Opt-out management (Reply STOP to unsubscribe)
Chatbot handoff flows
Setting up inbound SMS:
Purchase a long code or short code from the TechTo dashboard.
Register an inbound webhook URL under Developer → Webhooks → Inbound SMS.
TechTo calls your webhook with every inbound message in real time.
Inbound message payload:
json
{
"event": "message.inbound",
"from": "+919876543210",
"to": "TECHTO",
"body": "CONFIRM",
"received_at": "2025-07-03T10:05:22Z",
"message_id": "inbound_msg_ab4c91"
}Global Reach — 180+ Countries, Tier-1 Carrier Connections
While TechTo is purpose-built for India, the same API and credentials work for international messaging without any configuration changes.
International sending features:
180+ countries supported from a single API endpoint.
Geo-intelligent routing automatically selects the fastest, most cost-efficient carrier for each destination.
Local sender IDs available in select markets for higher open rates.
International number format validation — TechTo rejects malformed numbers at the API layer so you don't pay for undeliverable messages.
Unicode encoding for all regional scripts — Hindi, Tamil, Telugu, Arabic, Mandarin, Japanese, Korean, and more.
International pricing: International messages are priced per-destination-country. Full pricing for all 180+ supported countries is available in your dashboard under Settings → Pricing Table, or downloadable as a CSV for finance team review.
SMS Use Cases and Industry Solutions
OTP and Two-Factor Authentication
OTP delivery is the most latency-sensitive SMS use case. A 30-second delay on an OTP is the difference between a successful login and a frustrated user who churns.
TechTo's OTP-optimized routing prioritizes transactional traffic on dedicated carrier lanes — separate from promotional queues — ensuring OTPs are delivered within 2-3 seconds of the API call during peak traffic.
OTP best practices with TechTo:
Use the Transactional template category in DLT to bypass promotional filtering.
Keep OTP messages under 160 characters to avoid multi-segment billing.
Set OTP validity in the message itself (e.g., "Valid for 10 minutes").
Use TechTo's delivery webhook to detect failed OTP delivery and trigger a fallback (email, WhatsApp).
Never use alphanumeric sender IDs for OTPs in markets where numeric senders have higher trust scores.
E-Commerce — Order Lifecycle Notifications
Order confirmed → Packed → Shipped → Out for delivery → Delivered. Each stage is a touchpoint where SMS outperforms email by a factor of 5x in open rate.
TechTo e-commerce integration pattern:
Connect your order management system (Shopify, WooCommerce, Magento, custom) via TechTo's REST API or Zapier integration.
Create approved DLT templates for each order stage.
Trigger SMS automatically on order status change events.
Collect delivery receipts to confirm customer received each update.
Fintech and Banking
The RBI and SEBI both mandate specific timelines for transaction alert delivery. TechTo's transactional infrastructure is optimized for financial messaging compliance — ensuring debit/credit alerts, statement notifications, and account security warnings arrive within regulatory time windows.
Fintech-specific TechTo features:
Transaction alert templates pre-approved for banking category DLT registration.
High-priority transactional queue with guaranteed sub-5-second delivery SLA on Enterprise plans.
Redaction controls for masking account numbers and card digits in API logs.
Audit-ready delivery logs with carrier-level timestamps for regulatory reporting.
Healthcare — Appointment and Prescription Reminders
Studies consistently show that SMS appointment reminders reduce no-show rates by 35-45%. TechTo's scheduling feature lets healthcare providers send reminders at precisely the right intervals — 24 hours, 2 hours, and 30 minutes before appointments — with a single API call per booking.
EdTech and Education
Fee payment deadlines, exam schedules, result announcements, and class cancellations all carry urgency. TechTo's bulk API lets institutions reach tens of thousands of students and parents simultaneously, with per-recipient personalization, in seconds.
Logistics and Last-Mile Delivery
Real-time shipment updates, delivery window notifications, and proof-of-delivery confirmations build customer trust and reduce inbound support calls. TechTo's API integrates directly with major logistics platforms including Shiprocket, Delhivery, Ecom Express, and custom WMS systems.
Developer Resources — Everything You Need to Ship Fast
API Documentation
Comprehensive REST API documentation with interactive examples at docs.techtonetworks.com — built on OpenAPI 3.0 with a live Swagger UI. Test any endpoint directly from the docs without leaving your browser.
Postman Collection
Import TechTo's official Postman collection with a single click. All endpoints pre-configured with environment variables for sandbox and production. Download from the Developer section of your dashboard.
SDKs and Client Libraries
Official, actively maintained libraries for:
Language | Package | Install |
Python | techto-python | pip install techto-python |
Node.js | techto-node | npm install techto-node |
PHP | techto/php-sdk | composer require techto/php-sdk |
Java | Maven Central | groupId: com.techto |
Go | GitHub | |
Ruby | RubyGems | gem install techto |
All SDKs are open-source, MIT-licensed, and hosted on GitHub at github.com/techtonetworks.
Webhooks Testing Tool
Test your webhook endpoint without sending real messages. TechTo's webhook simulator lets you fire any event type (delivered, failed, inbound) to your local development server.
Works with ngrok out of the box:
bash
ngrok http 3000
# Copy the ngrok URL into TechTo Dashboard → Developer → Webhooks → Test WebhookSandbox Environment
The TechTo sandbox mirrors the production API exactly — same endpoints, same response format, same error codes — but no real messages are sent and no credits are consumed.
Sandbox virtual numbers: Test against any of TechTo's reserved sandbox phone numbers to simulate different delivery outcomes:
+919999999900 — Always delivers successfully
+919999999901 — Always fails (invalid number simulation)
+919999999902 — Delivers after a 5-second delay (network lag simulation)
+919999999903 — DND number simulation (blocked for promotional)
Status Page and Incident History
Real-time system status at status.techtonetworks.com — including API response time graphs, per-carrier delivery rate monitoring, and full incident history.
Integrations — Connect TechTo to Your Existing Stack
TechTo's send SMS API integrates with your existing tools without writing custom middleware.
CRM Integrations
Salesforce — Send SMS from workflows, triggers, and Process Builder automations.
HubSpot — Trigger SMS on lead status changes, deal stages, and contact activities.
Zoho CRM — Native Zoho integration with two-way SMS support.
Freshsales — SMS touchpoints directly within Freshsales sequences.
Marketing Automation
Zapier — 3,000+ app connections via TechTo's Zapier app. No-code SMS workflows in minutes.
Make (Integromat) — Advanced multi-step SMS automation scenarios.
ActiveCampaign — SMS as a channel within AC automation sequences.
E-Commerce Platforms
Shopify — Install TechTo's Shopify app for automated order, shipping, and delivery notifications.
WooCommerce — WordPress plugin with DLT template management built in.
Magento 2 — Full-featured extension for transactional and promotional SMS.
Developer Platforms
AWS Lambda — Invoke TechTo API directly from serverless functions.
Google Cloud Functions — Native REST API call within GCF workflows.
GitHub Actions — Trigger deployment alerts and build notifications via SMS.
PagerDuty — Escalate critical alerts to SMS when other channels fail.
TechTo vs. Competitors — Why Developers Switch
Feature | TechTo Networks | Twilio | Exotel | ValueFirst |
India DLT automation | ✅ Built-in | ❌ Manual | ✅ Built-in | ✅ Built-in |
DLT template manager | ✅ Yes | ❌ No | ✅ Yes | ✅ Limited |
Sandbox on signup | ✅ Instant | ✅ Yes | ❌ Requires approval | ❌ No |
Uptime SLA | 99.9% (99.99% Enterprise) | 99.95% | 99.9% | 99.5% |
Pricing (transactional) | From ₹0.18/SMS | From ₹0.55/SMS | From ₹0.24/SMS | From ₹0.20/SMS |
SMPP support | ✅ Enterprise | ✅ Enterprise | ✅ Yes | ✅ Yes |
Webhook signature verification | ✅ HMAC-SHA256 | ✅ Yes | ❌ No | ❌ No |
Free trial credits | 100 SMS free | Trial USD credits | Limited | No |
24/7 developer support | ✅ All plans | ❌ Paid tier only | ✅ Enterprise | ❌ Business hours |
Bulk batch API | ✅ 10,000/call | ✅ Yes | ✅ Yes | ✅ Limited |
Two-way messaging | ✅ Yes | ✅ Yes | ✅ Yes | ❌ Limited |
Pricing comparisons reflect publicly available information as of July 2025. International routes vary; see your TechTo dashboard for exact per-country pricing.
Customer Success Stories
Fintech Startup — 99.99% OTP Delivery at Scale
A leading digital lending platform was experiencing 8-12% OTP delivery failure with their previous provider during peak loan disbursement windows — causing application drop-offs and compliance issues.
After switching to TechTo's Enterprise plan with dedicated carrier connections:
OTP delivery rate improved from 91% to 99.99%
Average delivery latency dropped from 11 seconds to 1.8 seconds
Loan application completion rate increased by 22%
DLT compliance violations dropped to zero with TechTo's automated template validation
E-Commerce Platform — 500,000 Messages in 12 Minutes
A D2C fashion brand needed to send a festive sale announcement to their entire subscriber base of 500,000 customers simultaneously. Their previous provider throttled at 50 messages/second — making it a 3-hour operation that caused the promotion to miss peak traffic windows.
With TechTo's Growth plan batch API:
500,000 messages dispatched in 12 minutes
98.7% delivery rate (remaining 1.3% DND-filtered automatically)
Zero template rejections — all templates pre-registered via TechTo's DLT console
Cost: ₹60,000 (₹0.12/SMS promotional rate) vs ₹1,10,000 with previous provider
Healthcare Network — No-Shows Cut by 38%
A hospital chain with 14 facilities integrated TechTo's send SMS API into their appointment management system to send automated reminders 24 hours and 2 hours before appointments.
Results after 90 days:
No-show rate reduced from 22% to 13.6% — a 38% improvement
Staff time spent on manual reminder calls: reduced by 4 hours/day per facility
Patient satisfaction scores: +12 points on follow-up surveys
Frequently Asked Questions
How do I get started with TechTo's send SMS API? Sign up at techtonetworks.com/register — it takes under 60 seconds and requires no credit card. Your API key is generated automatically, and you can start testing in the sandbox immediately.
Do I need to complete DLT registration before sending SMS in India? For sending to Indian mobile numbers commercially, yes — TRAI's DLT mandate requires sender ID and template registration. TechTo's compliance team assists with the full DLT registration process and provides a built-in template management console to handle it without external portals. Sandbox testing does not require DLT registration.
What is the difference between the sandbox and production environments? The sandbox mirrors the production API exactly — same endpoints, same parameters, same response format — but no real messages are sent, no credits are consumed, and virtual test numbers simulate different delivery scenarios. Switch to production by changing sandbox: true to sandbox: false in your API call payload.
What programming languages does TechTo support? TechTo's API is REST-based over HTTPS, so any language that can make HTTP requests works — cURL, Python, Node.js, PHP, Java, Go, Ruby, C#, Swift, Kotlin, and more. Official SDKs are available for Python, Node.js, PHP, Java, Go, and Ruby.
What is the maximum throughput on the Growth plan? Growth plan accounts support up to 100 SMS/second via the HTTP API. Enterprise accounts support unlimited throughput via HTTP and up to 1,000+ messages/second via SMPP on dedicated connections. Contact sales for custom throughput configurations.
How are delivery receipts delivered? TechTo pushes delivery receipt events to your registered webhook URL in real time. Alternatively, you can poll the message status endpoint using the message_id returned in the original send response. Webhooks are strongly recommended for production systems.
Does TechTo support two-way SMS messaging? Yes. Two-way messaging is available on Growth and Enterprise plans using TechTo virtual numbers or short codes. Inbound messages are pushed to your registered inbound webhook URL in real time.
Can I schedule messages for future delivery? Yes. Include a send_at parameter with an ISO 8601 UTC timestamp in your API request. Scheduled messages can be cancelled anytime before dispatch using a DELETE request with the message_id.
Does TechTo support sending SMS in regional languages? Yes. TechTo automatically detects non-GSM-7 content and switches to Unicode encoding. You can also force Unicode with the unicode: true parameter. Regional script messages are limited to 70 characters per segment (67 for multi-part). Supported scripts include Hindi (Devanagari), Tamil, Telugu, Kannada, Malayalam, Bengali, Gujarati, Punjabi (Gurmukhi), Arabic, Chinese, Japanese, and more.
What security certifications does TechTo hold? TechTo is ISO 27001 certified, GDPR compliant, and PCI-DSS compliant. SOC 2 Type II reports are available to Enterprise customers under NDA. All API traffic runs over TLS 1.3, and webhook payloads are signed with HMAC-SHA256.
What happens to my messages if there is a carrier outage? TechTo's multi-carrier failover engine automatically reroutes affected messages to the next-best carrier route within milliseconds of detecting a delivery failure. No action is required from your side. Enterprise accounts have access to 5+ carrier routes per destination network.
Can I use TechTo's API to send international SMS? Yes. The same API key and endpoints work for 180+ countries globally. Geo-intelligent routing automatically selects the optimal carrier for each international destination. International pricing per country is available in your dashboard.
What is your refund policy for undelivered messages? Messages that fail after all failover attempts have been exhausted and are returned with a failed delivery status are not charged. You are only billed for successfully dispatched messages (status: dispatched or delivered). Enterprise SLA credit-backs apply for systemic delivery failures attributable to TechTo's infrastructure.
How does TechTo handle opt-outs and DND numbers? For promotional SMS, TechTo automatically checks recipient numbers against the TRAI DND registry before dispatch. DND-registered numbers are filtered and returned with a dnd_filtered status — not billed. For two-way messaging, inbound STOP/UNSUBSCRIBE keywords are detected and the number is automatically added to your account's suppression list.
Is there a free trial? Yes. Every new account receives 100 free SMS credits on signup — no credit card required. These credits work in both sandbox and production environments and can be used to test end-to-end delivery on real phone numbers.
Ready to Send? Start in Seconds.
You've read how TechTo's send SMS API works. Here's the only question left: why haven't you started yet?
Your free API key is 60 seconds away.
100 free SMS credits — no card needed
Sandbox live immediately on signup
Full DLT compliance support from day one
99.9% uptime SLA from your first message
Pricing that scales down as your volume scales up
Not ready to commit? That's fine too.
→ Read the Full API Documentation — no account required.
→ Talk to a Developer Advocate — free 30-minute integration consultation.
→ View Full Pricing Table — transparent, no hidden fees.
TechTo Networks — India's Developer-First SMS API Platform. Sub-second delivery. Automated DLT compliance. Pay as you go.
Comments