SpringEdge APIs follow standard REST conventions — JSON request/response format, HTTP status codes, and Bearer token authentication. Every API endpoint is accessible over HTTPS and returns structured responses with message IDs, delivery status, and credit usage.
SDKs are available for PHP, Python, Java, Node.js, Ruby, Go, and C#/.NET. For platforms without an SDK, any HTTP client (cURL, Postman, or your language's built-in library) works out of the box.
RESTful JSON API
Standard HTTP methods, JSON payloads, and predictable URL structure
API Key Authentication
Bearer token auth — generate and manage keys from your dashboard
Webhook Callbacks
Real-time delivery reports and incoming message events pushed to your server
Available APIs
Each API handles a specific communication channel. All APIs share the same authentication, response format, and webhook structure.
SMS API
Send transactional SMS, OTP codes, and promotional bulk campaigns. Supports Unicode, scheduled delivery, DLT templates, and DND filtering.
RCS API
Send rich cards, image carousels, suggested replies, and action buttons. Includes automatic SMS fallback for non-RCS devices.
Voice API
Automated voice broadcasting with text-to-speech in 15+ languages. Build IVR menus, collect DTMF input, and schedule calls.
WhatsApp API
Official WhatsApp Business API for template messages, rich media, interactive buttons, and automated chatbot conversations.
// Send SMS — cURL example
curl -X POST https://api.springedge.com/v1/sms/send \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '{
"to": "+919876543210",
"sender_id": "SPREDG",
"message": "Your OTP is 482910",
"type": "transactional"
}'
// Response
{
"status": "success",
"message_id": "msg_a1b2c3d4",
"credits_used": 1
}SMS API
Send an SMS with One API Call
The SMS API accepts a POST request with the recipient number, sender ID, message body, and message type (transactional or promotional). The API validates DLT template compliance, selects the optimal delivery route, and returns a message ID for tracking.
Delivery status is available via polling (GET request with the message ID) or automatically pushed to your webhook endpoint within seconds of delivery.
WHATSAPP API
Send WhatsApp Messages via API
The WhatsApp API sends pre-approved template messages with dynamic parameters. Templates support text, images, documents, videos, and interactive buttons (quick reply, call-to-action, URL). Each template must be approved by Meta before use.
Session messages (replies within 24 hours of a user-initiated conversation) support free-form text and media without template restrictions.
// Send WhatsApp template message
curl -X POST https://api.springedge.com/v1/whatsapp/send \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '{
"to": "+919876543210",
"template": "order_confirmation",
"params": {
"order_id": "ORD-78542",
"amount": "2,499",
"delivery": "Feb 28, 2026"
}
}'
// Response
{
"status": "success",
"message_id": "wa_x9y8z7w6"
}Developer Tools & Infrastructure
Everything you need to integrate, test, and monitor messaging in production.
SDKs & Libraries
Official libraries for PHP, Python, Node.js, Java, Ruby, Go, and C#/.NET. Install via pip, npm, composer, or Maven and start sending in minutes.
Sandbox Environment
Test your integration without sending real messages or using credits. Full API parity with production — same endpoints, same response format.
Webhooks & Events
Receive delivery reports, read receipts, and incoming messages as HTTP POST callbacks to your server in real time.
Analytics Dashboard
Track delivery rates, message latency, channel-wise usage, and credit consumption from a single dashboard with exportable reports.
Rate Limiting & Throttling
Configurable rate limits per API key. Default limits handle most use cases — contact support for higher throughput requirements.
Request Logging
Every API request and response is logged and accessible from your dashboard for debugging, auditing, and compliance purposes.
# Python example
import springedge
client = springedge.Client("YOUR_API_KEY")
response = client.sms.send(
to="+919876543210",
sender_id="SPREDG",
message="Your OTP is 482910",
msg_type="transactional"
)
print(response.message_id)
# "msg_a1b2c3d4"SDKs
Native Libraries for Every Stack
Our SDKs wrap the REST API into language-native classes and methods. Handle authentication, request construction, error handling, and response parsing automatically — so you can focus on building your application logic.
Available for PHP (Composer), Python (pip), Node.js (npm), Java (Maven), Ruby (gem), Go (module), and C#/.NET (NuGet). Each SDK includes typed models, async support, and retry logic built in.
Frequently Asked Questions
Common questions about SpringEdge API integration, authentication, and developer tools.
-
What programming languages does the SpringEdge API support?
SpringEdge provides a RESTful HTTP API that works with any programming language capable of making HTTP requests. We offer ready-to-use code examples and SDKs for PHP, Python, Java, Node.js, C#, Go, Ruby, and cURL. Since the API uses standard HTTP POST/GET requests with JSON responses, it integrates seamlessly into any technology stack — whether you're building a web application, mobile app, or backend service.
-
How do I authenticate with the SpringEdge API?
Authentication is done using an API key that is generated when you create your SpringEdge account. You include this API key as a parameter in every API request. All API calls must be made over HTTPS to ensure your credentials and message data are encrypted in transit. You can regenerate your API key from the dashboard at any time if it is compromised. No OAuth or complex authentication flows are required — simply sign up, get your API key, and start sending messages immediately.
-
Does SpringEdge provide webhooks for delivery reports?
Yes, SpringEdge supports real-time delivery report (DLR) webhooks for SMS, Voice, and WhatsApp messages. You configure a callback URL in your account settings, and the platform sends an HTTP POST request to that URL every time a message status changes — delivered, failed, rejected, or read (for WhatsApp). This lets your application track delivery status in real time without polling. The webhook payload includes the message ID, recipient number, status code, timestamp, and error details for failed messages.
-
Can I integrate SpringEdge with my CRM or ERP system?
Yes, SpringEdge integrates with popular business software through pre-built plugins and the REST API. We offer ready-made add-ons and plugins for WooCommerce, Magento, OpenCart, WordPress, and other platforms. For CRM systems like Salesforce, HubSpot, Zoho, and Tally, you can use our API to trigger automated messages based on CRM events — new lead created, deal closed, payment received, support ticket updated, and more. Any software that can make HTTP requests can integrate with SpringEdge in minutes.
-
What is the API uptime and response time?
SpringEdge guarantees 99.99% API uptime backed by redundant, carrier-grade infrastructure. The average API response time is under 5 milliseconds for message submission requests. Our platform is built on a distributed architecture with automatic failover, so even during maintenance windows or infrastructure incidents, your API calls continue to work. We process billions of messages annually across SMS, Voice, and WhatsApp channels.
-
Is there a sandbox or test environment for the API?
Yes, when you create a free SpringEdge account, you receive complimentary test credits that let you try all services — SMS, Voice, and WhatsApp — without any upfront payment or credit card. You can use these credits to test API integration, verify message delivery, and validate your application logic before going into production. The test environment uses the same API endpoints as production, so there is no code change needed when you switch to live messaging.