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 Location retrieval API

Retrieve the location of a device

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

This API exposes 1 operation across 1 path, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 0.4.0.

Requests are made against a single base URL, https://api-eu.vonage.com/network-location/v0.1.

1 operations 1 paths 11 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.4.0
Base URL
https://api-eu.vonage.com/network-location/v0.1
Authentication
HTTP Bearer
License
Resource Areas
1

Authentication & Security 1

Vonage Location retrieval API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth).

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Location Retrieval 1

Retrieve the location of a device

POST
/retrieval
Retrieve the location of a user’s mobile device based on their phone number
retrieveLocation body → 200400401403404415500503

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are ErrorResponse (4 properties), LocationCircle (3 properties), Point (2 properties), LocationPolygon (2 properties). Each schema is shown below with its type and property counts.

ErrorResponse
object
4 properties 2 required
PointList
array
List of points defining a polygon
Point
object
Coordinates (latitude, longitude) defining a location in a map
2 properties 2 required
LocationCircle
object
Location object
3 properties 3 required
LocationPolygon
object
Location object
2 properties 2 required
LastLocationTime
object
1 property
Polygon
Polygonal area
2 required
RetrievalLocationRequest
object
Request to retrieve the location of a phone number of an end-user device capable of connecting to a mobile network.
2 properties 1 required
Longitude
number
Longitude component of location
Circle
Circular area
2 required
Latitude
number
Latitude component of a location

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vonage-location-retrieval-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 Location retrieval 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.