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

Vezgo API

Vezgo API as documented publicly: 21 operations. Contract generated from the documentation by API Evangelist (2026-10-19); notthe provider's own document.

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

This API exposes 6 JSON Schema definitions.

The published artifact set on APIs.io includes an OpenAPI specification and 6 JSON Schemas.

This API exposes 21 operations across 20 paths, organized into 6 resource areas, and defines 12 schemas. It is described by OpenAPI 3.1.0, at version 2026-10-19.

Requests are made against a single base URL, https://api.vezgo.com.

21 operations 20 paths 12 schemas 1 DELETE14 GET5 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2026-10-19
Base URL
https://api.vezgo.com
Authentication
HTTP Bearer
Resource Areas
6

Authentication & Security 1

Vezgo API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearer). By default, every request must be authenticated.

Paths & Operations 21

Across 20 paths, the API surfaces 21 operations — 1 DELETE, 14 GET, 5 POST, 1 PUT. They span 6 resource areas: Accounts, Auth, Providers, Transactions, Vezgo, Wallet Connect. Each is listed below with its method, path, parameters, and response codes.

Accounts 10
GET
/accounts
All the user's accounts.
get_accounts → 200
POST
/accounts
Connect new account
post_accounts body → 201
PUT
/accounts/{id}
Update account credentials or answer security question
put_accounts_id 1 param body → 200
GET
/accounts/{id}/poll
Poll for an account update
get_accounts_id_poll 2 params → 200
DELETE
/accounts/{accountId}
Deletes the account.
delete_accounts_accountId 1 param → 200
GET
/accounts/{accountId}/history
The fiat value of each wallet over time.
get_accounts_accountId_history 4 params → 200
GET
/accounts/{accountId}/kyc-data
The identity data the provider holds.
get_accounts_accountId_kyc_data 1 param → 200
GET
/accounts/{accountId}/transactions/{txId}
One transaction.
get_accounts_accountId_transactions_txId 2 params → 200
GET
/v1/accounts
Get Started | Vezgo Docs
get_v1_accounts → 200
GET
/v1/accounts/613f3f9fe9b200002a0cc768
GET /v1/accounts/613f3f9fe9b200002a0cc768
get_v1_accounts_613f3f9fe9b200002a0cc768 → 200
Auth 2
POST
/auth/token
Create Users – Send a POST /auth/token request with the loginName in the header to obtain a bearer token.
post_auth_token 1 param body → 201
POST
/v1/auth/token
Get Started | Vezgo Docs
post_v1_auth_token 1 param body → 201
Providers 3
GET
/providers
Providers
get_providers 1 param → 200
GET
/providers/{name}
Providers
get_providers_name 1 param → 200
GET
/v1/providers
GET /v1/providers
get_v1_providers → 200
Transactions 1
GET
/transactions/{accountId}
Fetch transaction history for a specific account.
get_transactions_accountId 1 param → 200
Vezgo 4
POST
/vezgo/auth
POST /vezgo/auth
post_vezgo_auth body → 201
GET
/vezgo/callback
Redirect URI that handles the result of the Vezgo Connect flow.
get_vezgo_callback 6 params → 200
GET
/vezgo/connect
Backend endpoint that renders an auto‑submitting form to start the Vezgo Connect flow.
get_vezgo_connect → 200
POST
/vezgo/webhooks
Endpoint to receive webhook notifications from Vezgo.
post_vezgo_webhooks body → 201
Wallet Connect 1
GET
/wallet-connect/providers
Providers
get_wallet_connect_providers → 200

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are PostVezgoWebhooksRequest (4 properties), PostVezgoAuthRequest (2 properties), PostAuthTokenRequest (2 properties), PostV1AuthTokenRequest (2 properties). Each schema is shown below with its type and property counts.

PostAccountsRequest
object
1 property 1 required
PostAccountsResponse
object
1 property
PutAccountsIdRequest
object
2 properties
PutAccountsIdResponse
object
1 property
GetAccountsIdPollResponse
object
1 property
PostAuthTokenRequest
object
2 properties 2 required
PostAuthTokenResponse
object
1 property
PostV1AuthTokenRequest
object
2 properties 2 required
PostV1AuthTokenResponse
object
1 property
PostVezgoAuthRequest
object
2 properties 2 required
PostVezgoAuthResponse
object
1 property
PostVezgoWebhooksRequest
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vezgo-openapi-generated.yml Raw ↑

Other APIs Vezgo publishes across the network.

Vezgo API
Where this information came from

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