Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Communications / Nexmo / Nexmo Dispatch API
Nexmo Dispatch API logo

Nexmo Dispatch API

Browse all Nexmo APIs
76
AI ReadinessAI-Ready (A-)76/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticCommunicationsChat Messagingbasic, bearer1 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

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

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Nexmo Dispatch API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Nexmo Dispatch API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnexmo.com%2Fnexmo-dispatch-api" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnexmo.com%2Fnexmo-dispatch-api" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Nexmo Dispatch 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

Receive Messages API webhooks for each leg of the workflow tied to the parent dispatch_uuid

Use Cases

Patterns agents use Nexmo Dispatch 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

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

D

Dispatch API

- AI-Ready (A-)
76/100
93
Foundational Compliance
75
Developer Experience & Jentic Compatibility
75
AI-Readiness & Agent Experience
94
Agent Usability
43
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
93

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

75

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4
56%

Example Density

How richly the API is illustrated with examples.

96%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

75

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: A-Signals: 4
52%

Description Coverage

Coverage of descriptions across API elements.

100%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

43

Security

Trust, risk posture, and security compliance.

Grade: D-Signals: 1
42%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Nexmo Dispatch API by hand means supporting both HTTP basic and JWT bearer auth, minting per-call JWTs from your Application signing key, and posting failover workflows to the api.nexmo.com/v0.1/dispatch host. Through Jentic you install once, import the Dispatch API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

The Dispatch API exposes a single failover-workflow endpoint and takes the message template in the request body, so scoping is by operation rather than by resource: limit the agent to the operation it needs, which is posting a multi-channel failover workflow. That single dispatch call is the only thing it can run.

Credential isolation

Your Nexmo basic credentials and Application signing key are stored once, encrypted, by your own Jentic One instance and used to mint per-call JWTs at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'send a failover multichannel message', and Jentic returns the POST / operation with its full workflow body schema, including the nested failover template fields, so the agent calls the right endpoint without browsing the reference docs.

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 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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Nexmo Dispatch API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. The Dispatch API exposes just one operation, POST / to create a multi-channel failover workflow, so you scope by operation: allow the agent that single dispatch call and nothing else. The Nexmo basic credentials and Application signing key stay in your instance and are used to mint per-call JWTs at execution time, so the agent can post a failover workflow without ever handling the raw secrets.

GET STARTED

Start building with Nexmo Dispatch API

Explore with Jentic One
View OpenAPI Document