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

Two-factor authentication and phone verification

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

Tagged areas include Verify. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.

This API exposes 4 operations across 4 paths, and defines 3 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

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

4 operations 4 paths 3 schemas 1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://rest.nexmo.com
Authentication
HTTP Basic, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 2

Vonage Verify API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • basicAuth — Base64-encoded API key and secret joined by a colon.
  • bearerAuth — JWT token for application-level authentication.

Paths & Operations 4

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

Verify 4

Two-factor authentication and phone verification

POST
/verify/{format}
Request a Verification
requestVerification 1 param body → 200
POST
/verify/check/{format}
Check a Verification Code
checkVerification 1 param body → 200
GET
/verify/search/{format}
Search Verifications
searchVerification 4 params → 200
POST
/verify/control/{format}
Control a Verification
controlVerification 1 param body → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are VerifySearchResponse (12 properties), VerifyCheckResponse (5 properties), VerifyResponse (3 properties). Each schema is shown below with its type and property counts.

VerifyResponse
object
3 properties
VerifySearchResponse
object
12 properties
VerifyCheckResponse
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vonage-verify-api-openapi.yml Raw ↑

Other APIs Vonage publishes across the network.

Vonage Conversations API
Vonage Reports API
Vonage Video API
Vonage Applications API
Vonage Messages API
Vonage Numbers API
Vonage SMS API
Vonage Voice API
Where this information came from

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