SMS API alongside your WhatsApp API, for messages that always arrive
Add SMS via API to your multichannel flow next to your WhatsApp API and reach whoever did not reply on WhatsApp: no app, no internet, no dependence on a single channel.
- Availability: 99.9% uptime
- Reach: No app or data needed
- Strategy: Multichannel
You shouldn't be solving this.
Problems D-API takes off your plate.
Critical messages that never get read
Important notifications get stuck in WhatsApp or email and the customer simply does not see them. You need a channel that arrives even without an app installed.
Depending on a single channel
When all communication relies on one channel, any instability leaves customers uninformed. You are missing a recovery layer for whoever did not reply.
SMS stuck outside your automation
Sending SMS from spreadsheets or a manual dashboard does not scale and does not talk to your flow. You want SMS via API, integrated with the rest of the process.
From zero to production in four steps.
Generate your API key
Create your access credential on the D-API platform and authenticate your SMS requests securely.
Check the docs
Explore the SMS endpoints, parameters and responses in the OpenAPI 3 reference before integrating.
Read the docsPlug it into your flow
Connect SMS to your automation and to the D-API platform to use it as the backup channel for whoever did not reply on WhatsApp.
See integrationsSend and track
Send in bulk via API and monitor delivery reports in real time to fine-tune your multichannel strategy.
import { DApi } from 'd-api-sdk'
const dapi = new DApi({ apiKey: process.env.DAPI_API_KEY })
const { messageId } = await dapi.sms.send({
to: '14155550123',
text: 'Your access code is 482913',
route: 'otp', // transactional; the default is 'marketing'
})
// delivery status arrives at your SMS webhook (sms.delivered)curl -X POST https://api.d-api.cloud/api/v1/sms/send \
-H "Authorization: $DAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"to": "14155550123", "text": "Your access code is 482913", "route": "otp"}'import os
import requests
API = "https://api.d-api.cloud/api/v1"
HEADERS = {"Authorization": os.environ["DAPI_API_KEY"]}
sms = requests.post(f"{API}/sms/send", headers=HEADERS, timeout=10, json={
"to": "14155550123",
"text": "Your access code is 482913",
"route": "otp",
}).json()<?php
use GuzzleHttp\Client;
$dapi = new Client([
'base_uri' => 'https://api.d-api.cloud/api/v1/',
'headers' => ['Authorization' => getenv('DAPI_API_KEY')],
'timeout' => 10,
]);
$sms = json_decode($dapi->post('sms/send', ['json' => [
'to' => '14155550123',
'text' => 'Your access code is 482913',
'route' => 'otp',
]])->getBody(), true);Works with the tools you already use
- REST API
- n8n
- Make
- Zapier
- Webhook
The layer that reaches everyone.
SMS via REST API
Send SMS straight from your application with a REST API documented in Swagger, authenticated by API key. No manual dashboard, no middleman.
Universal reach
SMS arrives even without an app installed or internet on the device. It is the channel that reaches practically any number, in any context.
Backup and recovery layer
Use SMS as the recovery step of your multichannel flow: send to whoever did not reply on WhatsApp and make sure the message is not lost.
Multichannel on one platform
SMS lives alongside WhatsApp and IVR on the same D-API platform. Orchestrate channels together, without stitching different vendors.
Real-time delivery reports
Track delivery of every send in real time and know exactly what arrived, so you can trigger the next step of the flow with confidence.
Fits your automation
Schedule and integrate sends with n8n, Make, Zapier and the D-API platform itself, fitting SMS into the flow you already use.
Frequently asked questions.
How does bulk SMS via API work?
Does SMS arrive even without internet on the phone?
Can I use SMS together with WhatsApp on the same platform?
Can I plug SMS sending into my automations?
How do I know whether messages were delivered?
Ready to go to production?
3-day free trial with full access. No credit card, no lock-in.
