Virtual Peaker Pairing Code Device Discovery - End User App API
The [pairing code](./device-partner-api.html#section/Pairing-Codes) device discovery flow works as follows:1. The device owner fills out an onboarding form on Virtual Peaker's site.2. At the end of the form, we provide them with a pairing code and instructions to enter it in the Device Partner's app.3. Optionally, the user selects which devices to enroll via the Device Partner's interface. Otherwise, all devices are enrolled by default.4. When the user enters the pairing code in the Device Partner's app, the Device Partner publishes a device enrollment event to Virtual Peaker's API.5. The publish event includes the pairing code, allowing Virtual Peaker to link the device back to the onboarding form entry.6. If multiple devices are enrolled, the same pairing code is used in each publish payload.7. Virtual Peaker discovers the user details associated with the enrolled device(s).8. We subscribe to the devices for data publishing and provide a `DEVICE_PUBLISH_SECRET`.The user experience is driven through the Device Partner's web or mobile app after receiving the pairing code. This links together the Virtual Peaker and Device Partner platforms.
Virtual Peaker Pairing Code Device Discovery - End User App API is one of 8 APIs that Virtual Peaker publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, an engineering blog, and a getting-started guide.
This API exposes 1 operation across 1 path, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 2.0.6.
Requests are made against a single base URL, https://example.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Virtual Peaker Pairing Code Device Discovery - End User App API declares
2 security schemes
for authenticating requests.
It supports OAuth 2.0 (device_partner_api_auth) using the clientCredentials flow, exposing 1 scope.
It supports OAuth 2.0 (device_partner_user_auth) using the authorizationCode flow, exposing 1 scope.
By default, every request must be authenticated.
device_partner_user_auth— If using the OAuth onboarding method, this authentication method is used for the respective endpoints. Please the the FAQ for more details.
Paths & Operations 1
Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.
The [pairing code](./device-partner-api.htmlsection/Pairing-Codes) device discovery flow works as follows: 1. The device owner fills out an onboarding form on Virtual Peaker's sit…
Schemas 3
The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are UserDetails (6 properties), ServiceAddress (6 properties), Details (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Virtual Peaker 7
Other APIs Virtual Peaker publishes across the network.
This is an independent, third-party profile of Virtual Peaker Pairing Code Device Discovery - End User App 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.