How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Vonage Secret Management API

Many of the Vonage APIs are accessed using an API key and secret. It is recommended that you change or "rotate" your secrets from time to time for security purposes. This section provides the API interface for achieving this.Note: to work on secrets for your secondary accounts, you may authenticate with your primary credentials and supply the secondary API keys as URL parameters to these API endpoints.

Vonage Secret Management API is one of 59 APIs that Vonage publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

This API exposes 74 JSON Schema definitions.

Tagged areas include Secret Management. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an AsyncAPI specification, and 74 JSON Schemas.

This API exposes 4 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.4.

Requests are made against a single base URL, https://rest.nexmo.com.

4 operations 2 paths 5 schemas 1 DELETE2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.4
Base URL
https://rest.nexmo.com
Authentication
HTTP Basic
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Vonage Secret Management API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 1 DELETE, 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Secret Management 4

Many of the Vonage APIs are accessed using an API key and secret. It is recommended that you change or "rotate" your secrets from time to time for security purposes. This section…

GET
/accounts/{api_key}/secrets
Retrieve API secrets
retrieveAPISecrets 1 param → 200401404429500
POST
/accounts/{api_key}/secrets
Create API secret
createAPISecret 1 param body → 201400401404429500
GET
/accounts/{api_key}/secrets/{secret_id}
Retrieve API secret
retrieveAPISecret 2 params → 200401404429500
DELETE
/accounts/{api_key}/secrets/{secret_id}
Revoke API secret
revokeAPISecret 2 params → 204400401403404429500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are HalLink (5 properties), ErrorResponse (4 properties), SecretInfo (3 properties), SelfLink (1 property). Each schema is shown below with its type and property counts.

SelfLink
object
Link to the current resource (always required in HAL)
1 property 1 required
_links
object
HAL Links object
ErrorResponse
object
Base error response following RFC 7807
4 properties 3 required
HalLink
object
A single HAL link object
5 properties 1 required
SecretInfo
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vonage-secret-management-api-openapi.yml Raw ↑

Other APIs Vonage publishes across the network.

Vonage Account API
Vonage Advanced API
Vonage Application API
Vonage Applications API
Vonage Archives API
Vonage Audio Connector API
Vonage Balance API
Vonage Basic API
Vonage Broadcast API
Vonage Calls API
Vonage Configuration API
Vonage Conversation API
Where this information came from

This is an independent, third-party profile of Vonage Secret Management API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.