A production-grade SMPP server with parallel HTTP/REST API — for businesses, aggregators and OTT platforms that need reliable SMS delivery without running their own infrastructure. Bind in 1 hour, scale to 5,000 TPS.
Most enterprise integrations use SMPP for its persistent binding and high throughput. Use the HTTP API for quick-start, low-volume or stateless workloads. We give you both — same account, same routes, same DLRs.
Persistent TCP bind for high-throughput, low-latency SMS submission. Industry-standard protocol used by every tier-1 carrier.
Stateless HTTPS endpoint for simple integration — perfect for low-volume, transactional or webhook-driven use cases.
P95 submit_sm acknowledgement under 200 ms from any global region.
Direct routes to all major destinations + smart fallback for niche ones.
Web dashboard with TPS graphs, DLR breakdown, balance and rate-sheet exports.
Multi-route LCR engine fails over instantly when a route degrades.
Start prepaid with $500. NET 7 / NET 30 once volume justifies.
Per-bind throttling, content filters and abuse protection built-in.
Inbound MO routing to your HTTP webhook or SMPP receive bind.
Telegram & email response in < 15 minutes from real engineers.
Volume, target countries, traffic type. We send a custom rate sheet within 24 hours.
Quick MSA + NDA. Prepaid top-up via wire / crypto / card. Test credit included for new accounts.
SMPP host, port, system_id and password — or HTTP bearer token. Sandbox + production.
Connect, send, watch DLRs in the portal in real-time. NOC available 24/7.
Plug your existing platform into our gateway in minutes — Kannel, Jasmin, NowSMS, Sinch, Tyntec or your own custom ESME. SMPP 3.4 (3.3 supported on request) over TCP / TLS.
Tell us your volume and use case — we'll respond within 24 hours.
curl -X POST https://api.lcrone.com/v1/sms/send \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"from": "MyCompany",
"to": "+918888888888",
"text": "Your OTP is 4827. Valid for 5 minutes."
}'
SDKs & complete API reference shared after onboarding.
SMPP is a persistent TCP binding — better for high-throughput, low-latency workloads (5,000+ TPS). HTTP API is stateless — easier to integrate but adds ~50ms per request and is better suited for <100 TPS. Same routes, same DLRs, you can use both.
Within 1 hour of contract signing and prepaid top-up. Sandbox bind for testing is issued immediately for qualified inquiries.
Yes — TLS 1.2 / 1.3 on port 3550 (in addition to plain TCP on 2775). Recommended for production deployments.
Yes — any standards-compliant SMPP client works. We've onboarded clients running Kannel, Jasmin, NowSMS, Sinch, Tyntec, Twilio Notify, and many custom-built ESMEs.
Carrier-confirmed DLR on SS7 routes (~95-100% accuracy). Smart-inference DLR on routing routes. Both delivered as standard SMPP deliver_sm or HTTP webhook.
Yes — qualified prospects get a sandbox bind with $20 of test credit before signing the production agreement.
SMPP bind or HTTP API key — your choice. Test credit included for qualified accounts.
Get Started →