Vonage Voice API (via KPN)
The Voice API lets you create outboud calls, control in progress calls and get information about current and historical calls. The API is divided in 2 big resources blocks: - Application: Manage application level options - Call: Manage call level options ## Call Guidelines 1. Create an application 2. Make a call ## Guidelines to create an application In order to create an application, we need to provide 3 values: - name - type (voice) - answer_url - event_url For more information regarding the meaning of each field, refer to the POST /application endpoint. Among the return values of this call, there is the application identifier (uuid). It is needed to make calls or to operate with the application. ## Guidelines to make a call In order to make a call, we must include the identifier of the application in the **header** and fill the basic fields from the...
Vonage Voice API (via KPN) is one of 38 APIs that KPN publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Voice, CPaaS, and Resold API. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.
This API exposes 15 operations across 8 paths, organized into 3 resource areas, and defines 25 schemas. It is described by OpenAPI 3.0.0, at version v1.1.1.
Requests are made against a single base URL, https://api-prd.kpn.com/communication/nexmo/.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Vonage Voice API (via KPN) declares
1 security scheme
for authenticating requests.
It supports OAuth 2.0 (oauth2) using the clientCredentials flow.
Paths & Operations 15
Across 8 paths, the API surfaces 15 operations — 3 DELETE, 5 GET, 2 POST, 5 PUT. They span 3 resource areas: voice, applications, JWT. Each is listed below with its method, path, parameters, and response codes.
Call related resource management
Application related resource management
Call to generate JWT.
Schemas 25
The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are call (13 properties), callEvent (7 properties), application (5 properties), NCCO (4 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from KPN 12
Other APIs KPN publishes across the network.
This is an independent, third-party profile of Vonage Voice API (via KPN), 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.