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 Account API

An external-account used as the `from` field in the Messages API and Dispatch API

Vonage Account 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 Account. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an AsyncAPI specification, and 74 JSON Schemas.

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

Requests are made against 2 base URLs: https://api.nexmo.com/beta/chatapp-accounts, https://rest.nexmo.com.

2 operations 2 paths 10 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.nexmo.com/beta/chatapp-accounts
Authentication
HTTP Bearer, HTTP Basic
Resource Areas
1

Authentication & Security 2

Vonage Account API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). It accepts HTTP basic authentication (basicAuth).

Paths & Operations 2

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

Account 2

An external-account used as the from field in the Messages API and Dispatch API

GET
/
Retrieve all accounts you own
GetAllAccounts 3 params → 200401
GET
/account/numbers
List the numbers you own
getOwnedNumbers 7 params → 200401

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are ownednumber (11 properties), MessengerAccountResponse (6 properties), WAAccountResponse (5 properties), VSMAccountResponse (5 properties). Each schema is shown below with its type and property counts.

401Response
object
2 properties
MessengerAccountResponse
object
6 properties 4 required
WAAccountResponse
object
5 properties 3 required
VSMAccountResponse
object
5 properties 3 required
GetAllAccountResponse
account-unauthorized
object
2 properties
inbound-numbers
object
2 properties
country
string
The two character country code in ISO 3166-1 alpha-2 format
number-limitation
object
3 properties 3 required
ownednumber
object
11 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vonage-account-api-openapi.yml Raw ↑

Other APIs Vonage publishes across the network.

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
Vonage Dial In Numbers API
Where this information came from

This is an independent, third-party profile of Vonage Account 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.