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

Volt Aliases API

Issuance and management of account aliases for global reconciliation.

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

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

This API exposes 6 operations across 5 paths, and defines 24 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://accounts.sandbox.volt.io, https://accounts.volt.io.

6 operations 5 paths 24 schemas 3 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://gateway.volt.io
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

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

Paths & Operations 6

Across 5 paths, the API surfaces 6 operations — 3 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Aliases 6

Issuance and management of account aliases for global reconciliation.

GET
/accounts/{accountId}/aliases
List of aliases for an account
get-aliases 5 params → 200400401403404405406415
POST
/orders/account-aliases
Order aliases
order-aliases 2 params body → 201400401403404405406409
GET
/orders/account-aliases/{id}
Get alias order status
get-alias-order-status 2 params → 200400401403404500
GET
/account-aliases/{aliasId}
Get alias details
get-alias-details 2 params → 200400401403404405406415
PATCH
/account-aliases/{aliasId}
Change state of alias
change-alias-state 3 params body → 200400401403404405406409
POST
/account-aliases/{aliasId}/close
Close alias
close-alias 3 params body → 200400401403404409415422

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are AliasOrderDetails (8 properties), AliasMinimalDetails (8 properties), Error422Response (3 properties), ValidationErrorDetail (3 properties). Each schema is shown below with its type and property counts.

Error401Response
object
Error response for HTTP 401 Unauthorized.
2 properties 2 required
Error403Response
object
Error response for HTTP 403 Forbidden.
2 properties 2 required
AliasMinimalDetails
object
8 properties
AliasOrderStatusEnum
string
Current status of the alias order
AliasOrderLinks
object
2 properties
Error500Response
object
Error response for HTTP 500 Internal Server Error.
2 properties 2 required
Communication
object
1 property
AliasDetails
object
Error422Response
object
Error response for HTTP 422 Unprocessable Entity.
3 properties 3 required
Error400Response
object
Error response for HTTP 400 Bad Request.
2 properties 2 required
ValidationErrorType
AliasOrderDetails
object
Alias order status and details.
8 properties
Identifications
array
A list of one or more account identifiers.
Error409Response
object
Error response for HTTP 409 Conflict.
2 properties 2 required
Error405Response
object
HTTP method is not supported for this URL.
2 properties 2 required
Error404Response
object
Error response for HTTP 404 Not Found.
2 properties 2 required
LinkObject
object
2 properties 1 required
CurrencyCode
string
Three-letter ISO 4217 currency code.
AliasCloseRequest
object
1 property
ChangeAliasStateRequest
object
1 property 1 required
Error415Response
object
Request contains data in an unsupported content type.
2 properties 2 required
ValidationErrorDetail
object
Details about a specific validation error.
3 properties
AliasesOrderRequest
object
3 properties 2 required
Error406Response
object
API is not able to generate a response in the format defined in the Accept HTTP request header.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

volt-io-aliases-api-openapi.yml Raw ↑

Other APIs Volt publishes across the network.

Volt Payments API
Volt Mandates API
Volt Verify API
Volt Reporting API
Volt Authentication API
Volt Account Holder Verification API
Volt Accounts API
Volt Named Accounts API
Volt Sandbox API
Volt Transactions API
Volt Trusted accounts API
Where this information came from

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