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 Named Accounts API

Named account order operations.

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

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

This API exposes 2 operations across 2 paths, and defines 15 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.

2 operations 2 paths 15 schemas 1 GET1 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 Named Accounts API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

Paths & Operations 2

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

Named Accounts 2

Named account order operations.

POST
/orders/named-accounts
Create named account order
create-named-account-order 3 params body → 202400401403404409422500
GET
/orders/named-accounts/{id}
Get named account order status
get-named-account-order-status 2 params → 200400401403404500

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are NamedAccountOrderDetails (7 properties), NamedAccountOrderRequest (3 properties), ValidationErrorDetail (3 properties), Error422Response (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
NamedAccountOrderRequest
object
Request to create a named account from an approved onboarding.
3 properties 2 required
NamedAccountOrderStatusEnum
string
Current status of the named account order
Error500Response
object
Error response for HTTP 500 Internal Server Error.
2 properties 2 required
Communication
object
1 property
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
Error409Response
object
Error response for HTTP 409 Conflict.
2 properties 2 required
Error404Response
object
Error response for HTTP 404 Not Found.
2 properties 2 required
CurrencyCode
string
Three-letter ISO 4217 currency code.
ValidationErrorDetail
object
Details about a specific validation error.
3 properties
NamedAccountOrderDetails
object
Named account order status and details.
7 properties
XVoltTestingScenario
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

volt-io-named-accounts-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 Aliases 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 Named Accounts 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.