Nexmo Dispatch API

Name: Nexmo Dispatch API API
Brand: Nexmo Dispatch API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsChat Messagingbasic, bearer1 EndpointsREST

For Agents

Send a message that automatically retries on the next channel (WhatsApp, SMS, Viber, Messenger) when the previous attempt fails or is not read in time. One POST endpoint.

Quickstart

Get started with Nexmo Dispatch API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send a failover multichannel message via nexmo dispatch"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Nexmo Dispatch API API.

Define a failover workflow with multiple ordered channel attempts via POST /

Configure a per-step condition_status (delivered or read) that counts as success

Set a failover_expiry per step after which Dispatch advances to the next channel

Authenticate using either basic auth or a JWT bearer token tied to a Nexmo application

GET STARTED

Start building with Nexmo Dispatch API API

Explore with Jentic

View OpenAPI Document

Use for: Send a WhatsApp message that falls back to SMS, Create a failover workflow with a 300-second WhatsApp expiry, Submit a multi-channel notification that escalates Viber to Messenger to SMS, Trigger a single dispatch workflow for a transactional alert

Not supported: Does not send single-channel messages directly, manage WhatsApp templates, or expose per-channel analytics dashboards — use only to define multi-channel failover workflows that delegate sending to the Messages API.

Jentic publishes the only available OpenAPI document for Nexmo Dispatch API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Nexmo Dispatch API, keeping it validated and agent-ready. This dispatch-api slug is the alternate-named copy of Nexmo's Dispatch service, which orchestrates multi-channel failover workflows on top of Messages. A workflow follows a template; the failover template specifies an ordered list of channel attempts where each step has a success condition and a per-step expiry. The single POST endpoint accepts the full workflow body and returns a dispatch_uuid for status tracking.

Use Cases

Patterns agents use Nexmo Dispatch API API for, with concrete tasks.

★ Failover messaging for high-priority alerts

Operations and security teams configure WhatsApp-then-SMS workflows so that critical alerts always reach an on-call engineer. The failover template handles the retry timer and channel switch in Nexmo's infrastructure, removing the need for application-side scheduling. POST / accepts the full ordered workflow in a single request.

POST to / with a workflow targeting the on-call engineer's WhatsApp first (condition delivered, expiry 180) and SMS second.

Read-confirmed customer notifications

For appointment confirmations or order updates, businesses can require a read condition on the first step so the workflow only stops once the customer has actually seen the message. If no read event lands within the failover_expiry, Dispatch falls over to SMS where read tracking is unavailable but delivery is reliable.

POST to / with a WhatsApp step having condition=read and failover_expiry=600, followed by an SMS fallback step using basic auth.

Single-call cross-channel send for AI agents

An agent that needs to reach a user reliably without owning retry logic can issue one Dispatch call through Jentic. Search by intent, load the workflow schema, submit the body — Nexmo handles the rest including webhook fan-in tied to a single dispatch_uuid.

Search Jentic for 'send a failover multichannel message', load POST /, and execute with a two-step workflow.

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for nexmo dispatch api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

Create a multi-channel failover workflow

POST

Create a multi-channel failover workflow

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Basic credentials and JWT signing keys are encrypted in the Jentic vault. Per-call JWTs are minted server-side and injected into the bearer header without ever leaving the vault boundary.

Intent-based discovery

Agents search by intent (e.g., 'send a failover multichannel message') and Jentic returns POST / with the full workflow body schema, including the nested failover template fields.

Time to first call

Direct integration: 1-2 days for JWT signing, webhook handling, and template construction. Through Jentic: under an hour — one search, one load, one execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Nexmo Messages API

The single-channel send API that Dispatch orchestrates across multiple channels

Use Messages when one channel is enough; use Dispatch when channel failover is required.

Alternative

Twilio API

Twilio Notify and Conversations cover similar multi-channel orchestration

Pick Twilio when the existing stack already uses Twilio Studio or Notify.

Alternative

Sinch

Sinch Conversation API offers comparable cross-channel routing for SMS, WhatsApp, RCS and Messenger

Choose Sinch when RCS support or carrier-direct routing matters more than Nexmo's failover template.

FAQs

Specific to using Nexmo Dispatch API API through Jentic.

Why is there no official OpenAPI spec for Nexmo Dispatch API?

Vonage (formerly Nexmo) does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Nexmo Dispatch API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Nexmo Dispatch API use?

Either HTTP basic auth using api_key and api_secret or HTTP bearer with an application-scoped JWT. Jentic stores the credential pair and the signing key encrypted, signs JWTs server-side per call, and never exposes either to the agent.

Can I configure how long Dispatch waits before falling over?

Yes. Each step in the workflow has a failover_expiry in seconds. If the configured condition (delivered or read) is not reached within that window, Dispatch advances to the next step automatically.

What are the rate limits for the Nexmo Dispatch API?

The OpenAPI spec does not declare rate limits. Limits are imposed at the account level and at the underlying Messages API channels (WhatsApp, SMS, Viber, Messenger), which apply to each dispatched leg.

How do I send a WhatsApp-to-SMS failover message through Jentic?

Search Jentic for 'send a failover multichannel message', load POST / on the Dispatch API, and execute it with template=failover and a workflow array containing the WhatsApp and SMS steps.

How does this dispatch-api slug differ from the dispatch slug?

They expose the same underlying API at the same base URL with the same single POST / endpoint. The two slugs exist because of how the spec was originally indexed; either path can be used to reach the same Dispatch service.