VoPay Partner Endpoints API
The Partner Endpoints API from VoPay — 14 operation(s) for partner endpoints.
VoPay Partner Endpoints API is one of 61 APIs that VoPay publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Partner Endpoints. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 15 operations across 14 paths. It is described by OpenAPI 3.2.0, at version 2.0.
Requests are made against a single base URL, https://earthnode-dev.vopay.com/api/v2.
Metadata
The identity and technical contract details declared by the specification.
Paths & Operations 15
Across 14 paths, the API surfaces 15 operations — 5 GET, 10 POST. Each is listed below with its method, path, parameters, and response codes.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from VoPay 12
Other APIs VoPay publishes across the network.
This is an independent, third-party profile of VoPay Partner Endpoints 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.