---
title: "SMS API | Multichannel backup for your WhatsApp API | D-API"
description: "D-API's SMS API: send via REST with universal reach, the backup layer of your WhatsApp API flow for contacts who did not reply. Real-time delivery reports."
url: https://d-api.cloud/en/sms-api
---

Solution · SMS

# 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

## Talk to our team

See how D-API fits into your product. Support in English, and we reply within 1 business day.

Short answer

## How do you send SMS via API?

Your application calls the D-API REST API, authenticated by your API key, with the recipient and the text, and tracks delivery in real time in the reports. SMS arrives even without an app installed or internet on the device, which is why it is often used as a backup layer for whoever did not reply on WhatsApp. Sends can also be orchestrated in n8n, Make or Zapier.

The problem

## You shouldn't be solving this.

Problems D-API takes off your plate.

1.  ### 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.
    
2.  ### 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.
    
3.  ### 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.
    

How it works

## From zero to production in four steps.

1.  ### Generate your API key
    
    Create your access credential on the D-API platform and authenticate your SMS requests securely.
    
2.  ### Check the docs
    
    Explore the SMS endpoints, parameters and responses in the OpenAPI 3 reference before integrating.
    
    [Read the docs](https://docs.d-api.cloud/)
    
3.  ### Plug 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 integrations](https://d-api.cloud/en/integrations)
    
4.  ### Send and track
    
    Send in bulk via API and monitor delivery reports in real time to fine-tune your multichannel strategy.
    

Node.jscURLPythonPHP

```
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

What you get

## The layer that reaches everyone.

-   ### SMS via REST API
    
    Send SMS straight from your application with a [REST API documented in Swagger](https://docs.d-api.cloud/), 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.
    

FAQ

## Frequently asked questions.

### How does bulk SMS via API work?

You send requests to the D-API REST API, authenticated by API key, with the recipients and the content. The platform processes the sends and you track delivery in real time. The full reference is in the [Swagger docs](https://docs.d-api.cloud/).

### Does SMS arrive even without internet on the phone?

Yes. SMS has universal reach and gets to the device even without an app installed or an internet connection. That is exactly why it works so well as the backup layer of your multichannel flow.

### Can I use SMS together with WhatsApp on the same platform?

Yes. At D-API, SMS lives alongside WhatsApp and IVR on the same platform, which lets you build a multichannel strategy. A common approach is to use SMS to reach whoever did not reply on WhatsApp.

### Can I plug SMS sending into my automations?

Yes. Sending is programmable and integrates with automation tools such as n8n, Make and Zapier, as well as the D-API platform itself. That way SMS fits into the flow you already run, with no manual process.

### How do I know whether messages were delivered?

The platform provides real-time delivery reports for every send. You know exactly what reached the recipient and can use that to trigger the next step of the flow with confidence.

## Related guides

-   [Verification codes](https://d-api.cloud/en/whatsapp-otp-verification)
-   [IVR and voice calls](https://d-api.cloud/en/ivr-voice-calls-api)
-   [Bulk messaging](https://d-api.cloud/en/whatsapp-bulk-messaging-api)
-   [Cart recovery](https://d-api.cloud/en/whatsapp-api-for-cart-recovery)

## Ready to go to production?

3-day free trial with full access. No credit card, no lock-in.

[Talk to sales](https://d-api.cloud/#lead)[Read the docs](https://docs.d-api.cloud/)