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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
VoPay

VoPay Contact API

VoPay's Contact API — 15 documented operation(s) across 15 path(s) on VoPay's API-first embedded finance platform for Canadian and cross-border money movement.

Documentation Provider Profile APIs.io OpenAPI GitHub

VoPay Contact API is one of 23 APIs that VoPay publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Contacts and Recipients. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 15 operations across 15 paths, organized into 3 resource areas. It is described by OpenAPI 3.0.0, at version 2.0.

Requests are made against a single base URL, https://earthnode-dev.vopay.com/api/v2.

15 operations 15 paths 0 schemas 5 GET10 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
2.0
Base URL
https://earthnode-dev.vopay.com/api/v2
Contact
API Support
Resource Areas
3

Paths & Operations 15

Across 15 paths, the API surfaces 15 operations — 5 GET, 10 POST. They span 3 resource areas: Contact Endpoints, Contact Notes Endpoints, Contact Labels Endpoints. Each is listed below with its method, path, parameters, and response codes.

Contact Endpoints 8
POST
/contacts/add
contacts/add
ContactAddPOST body → 200
POST
/contacts/edit
contacts/edit
ContactEditPOST body → 200
POST
/contacts/deactivate
contacts/deactivate
ContactDeactivatePOST body → 200
POST
/contacts/activate
contacts/activate
ContactActivatePOST body → 200
GET
/contacts
contacts
ContactGET 7 params → 200
GET
/contacts/payment-methods
contacts/payment-methods
ContactPaymentMethodsGET 4 params → 200
GET
/contacts/transactions
contacts/transactions
ContactTransactionsGET 13 params → 200
POST
/account/contact/generate-embed-url
account/contact/generate-embed-url
ClientAccountGenerateEmbedURLPOST body → 200
Contact Notes Endpoints 4
POST
/contacts/notes/add
contacts/notes/add
ContactNotesAddPOST body → 200
POST
/contacts/notes/edit
contacts/notes/edit
ContactNotesEditPOST body → 200
POST
/contacts/notes/delete
contacts/notes/delete
ContactNotesDeletePOST body → 200
GET
/contacts/notes
contacts/notes
ContactNotesGET 5 params → 200
Contact Labels Endpoints 3
GET
/contacts/label
contacts/label
ContactLabelGet 4 params → 200
POST
/contacts/label/add
contacts/label/add
ContactLabelAddPost body → 200
POST
/contacts/label/delete
contacts/label/delete
ContactLabelDeletePost body → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vopay-contact.json Raw ↑

Other APIs VoPay publishes across the network.

VoPay Accounts API
AE Profile APIs.io
VoPay Account Onboarding API
AE Profile APIs.io
VoPay Bill Pay API
AE Profile APIs.io
VoPay Blocked Accounts API
AE Profile APIs.io
VoPay Branding API
AE Profile APIs.io
VoPay Client Accounts API
AE Profile APIs.io
VoPay Convenience Fees API
AE Profile APIs.io
VoPay Dispute Management Endpoints API
AE Profile APIs.io
VoPay eLinx API
AE Profile APIs.io
VoPay File Conversion API
AE Profile APIs.io
VoPay Global Cash Management API
AE Profile APIs.io
VoPay Integrations and Support API
AE Profile APIs.io
#Contacts#Recipients
← Back to V APIs
API Details
ID
vopay:vopay-contact
Base URL
https://earthnode-dev.vopay.com/api/v2
Docs
https://docs.vopay.com/reference/getting-started-with-your-api
Provider
VoPay
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=vopay-contact&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/vopay-contact"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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