Nexmo Media API

Name: Nexmo Media API API
Brand: Nexmo Media API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaAudio Processingnone4 EndpointsREST

For Agents

List, retrieve metadata for, update, and delete media items (typically audio used by the Voice API) stored in Nexmo's media bucket. Four endpoints.

Connect the Nexmo Media API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Nexmo Media 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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Media API API.

List and search media items via GET / with optional filters

Retrieve a media item's metadata by id via GET /:id/info

Update a media item's metadata (title, mime type, etc.) via PUT /:id/info

Delete a media item from the bucket via DELETE /:id

GET STARTED

Start building with Nexmo Media API API

Explore with Jentic

View OpenAPI Document

Use for: List all media items stored on this Nexmo account, Retrieve metadata for a specific media item by id, Update the title of an audio file in Nexmo Media, Delete a media file that is no longer used by any Voice application

Not supported: Does not upload new media, transcribe audio, or play files into a call directly — use only to list, inspect, update metadata for, and delete media items already stored in the Nexmo bucket.

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

Jentic publishes the only available OpenAPI specification for Nexmo Media API, keeping it validated and agent-ready. The Media API stores and retrieves media items — most often audio files used by Nexmo's Voice API for prompts and recordings. Four endpoints cover listing and searching items, retrieving an item's metadata, updating that metadata, and deleting an item by id. The API is the storage layer that other Nexmo products read from when they need to play, record, or attach a media file.

Use Cases

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

★ Managing voice prompt audio files

Voice applications using Nexmo's NCCO talk and stream actions reference audio files stored in Media. Teams use GET / to list available prompts, GET /:id/info to inspect a specific file's metadata, and PUT /:id/info to rename prompts as their script evolves. Cleanup happens through DELETE /:id when prompts are retired.

GET / to list audio prompts, then PUT /:id/info on the matching id with the new title to rename a prompt.

Cleaning up call recordings

Long-running Nexmo Voice deployments accumulate call recordings in Media. Operations teams periodically GET / with date filters to find old recordings and DELETE /:id to remove items past retention. The API itself does not enforce retention; the application drives the cleanup logic.

GET / filtered to items older than the retention window, iterate the result, and DELETE /:id for each id.

Audit of media inventory by an AI agent

An AI agent answering 'how much media do I have stored on Nexmo?' can list items and retrieve each item's metadata through Jentic. Discovery is by intent; execution loops over the four endpoints without the agent constructing URL paths.

Search Jentic for 'list nexmo media items', load GET /, execute, then call GET /:id/info on each returned item to collect metadata.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

List and search media items

GET

/:id/info

Retrieve metadata for a media item

PUT

/:id/info

Update metadata for a media item

DELETE

/:id

Delete a media item

GET

List and search media items

GET

/:id/info

Retrieve metadata for a media item

PUT

/:id/info

Update metadata for a media item

DELETE

/:id

Delete a media item

Why though Jentic?

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

Credential isolation

Application JWT signing keys are stored encrypted in the Jentic vault. The bearer JWT for each Media call is minted server-side, so the agent never touches the application private key.

Intent-based discovery

Agents search by intent (e.g., 'delete a nexmo media item') and Jentic returns the matching endpoint among the four operations with its parameters, so the agent picks the right method without browsing developer.nexmo.com.

Time to first call

Direct integration: half a day to wire up JWT auth and pagination. Through Jentic: under 30 minutes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Nexmo Application API v2

Manages the applications whose Voice flows reference these media items

Use Application API to create or fetch the application; use Media to manage the audio it plays or records.

Alternative

Twilio API

Twilio's Recordings and Media resources offer comparable storage for call audio

Choose Twilio when call audio already lives on Twilio and a single vendor for voice and storage is preferred.

Alternative

Plivo

Plivo's Recordings API provides similar audio retrieval for voice deployments

Pick Plivo when its pricing on voice recording storage is more attractive for the workload.

FAQs

Specific to using Nexmo Media API API through Jentic.

Why is there no official OpenAPI spec for Nexmo Media 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 Media 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 Media API use?

The OpenAPI spec does not declare a securityScheme on these endpoints, but in practice the Vonage Media service requires the same JWT bearer authentication used by other application-scoped APIs. Through Jentic the JWT is signed and injected per call, so the agent never handles the application private key.

Can I upload new media items through this API?

No. The four endpoints in this spec cover listing, retrieving, updating, and deleting items. Uploads happen via the separate Vonage upload endpoint or are written by Voice itself when calls are recorded.

What are the rate limits for the Nexmo Media API?

The OpenAPI spec does not declare rate limits. Vonage applies account-level throttles, and because Media is metadata-heavy rather than transactional, callers rarely hit limits in normal usage.

How do I delete a stale call recording through Jentic?

Search Jentic for 'delete a nexmo media item', load DELETE /:id, and execute it with the id of the recording. To find candidates first, run GET / with a date filter and iterate the result.

How do I update the title of a media file?

PUT /:id/info accepts an updated metadata body for the item. The id stays the same, so any Voice NCCO that references it continues to work after the rename.