What authentication does the Nexmo Media API use?

The OpenAPI spec does not declare a securityScheme, but in practice the Vonage Media service requires application-scoped JWT bearer authentication. Through Jentic the JWT is minted from the encrypted private key per call, so the agent never sees the signing material.

Can I create or upload media items via this API?

No. The four endpoints handle listing, retrieving, updating, and deleting items. Uploads use a separate Vonage upload mechanism, and Voice writes recordings into the bucket automatically when calls are recorded.

What are the rate limits for the Nexmo Media API?

The OpenAPI spec does not declare rate limits for /v3/media. Account-level throttles apply; the metadata endpoints are typically called at low volume relative to message or voice traffic.

How do I delete an old call recording through Jentic?

Search Jentic for 'delete a nexmo media item', load DELETE /:id, and execute with the recording id. Use GET / first with a date filter to find candidate ids.

How does the media-api slug differ from the media slug?

Both slugs index the same /v3/media service with the same four endpoints. The duplication is from the original spec ingest; either slug points to the same operations and base URL.

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

Yes. Because you run Jentic One yourself, your own rules decide which of the four operations the agent may call, so you can allow it to list items with GET / and read metadata with GET /:id/info while withholding PUT /:id/info and DELETE /:id. Since the media item id sits in the URL path, a rule can also pin the agent to a single item, letting it read and update that item's metadata only. Deleting an item is never available unless you explicitly grant it.