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 Transactions API

Operations related to movement of funds, including payouts, settlements, and internal transactions.

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

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

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

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

Paths & Operations 3

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

Transactions 3

Operations related to movement of funds, including payouts, settlements, and internal transactions.

GET
/transactions
List of transactions
get-transactions 14 params → 200400401403405406415422
GET
/transactions/{transactionId}
Get transaction details
get-transaction-details 2 params → 200400401403404405406415
POST
/accounts/{accountId}/transactions
Create a transaction
create-transaction 5 params body → 201400401403404405406409

Schemas 44

The contract defines 44 schemas that model the data the API accepts and returns. The most detailed are TransactionMinimalDetails (20 properties), TransactionLinks (8 properties), Beneficiary (8 properties), RefundTransactionRequest (7 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
TransactionMinimalDetails
object
20 properties
Failure
object
Details regarding why a transaction was not successful.
1 property
TransactionTypeEnum
string
TransactionDetails
object
InternalTransactionRequest
object
7 properties 5 required
AccountHolderVerification
object
Account Holder Verification basic information.
3 properties
TransactionSubTypeEnum
string
Performer
object
3 properties
OutgoingTransactionRequestBeneficiary
object
4 properties 2 required
Error500Response
object
Error response for HTTP 500 Internal Server Error.
2 properties 2 required
TransactionOperationEnum
string
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
SortOrder
string
Sorting direction
ValidationErrorType
TransactionStatusEnum
string
Beneficiary
object
The recipient of the funds.
8 properties
InternalReference
stringnull
Unique identifier of the transaction in the partner's system. Useful for automated reconciliation and logging.
VerificationResult
string
The outcome of the Account Holder Verification (AHV) process. This indicates the degree of similarity between the provided beneficiary name and the name regist…
InitiatedBy
object
1 property
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
Alias
object
Account alias details associated with the transaction.
1 property
Sender
object
4 properties
Error404Response
object
Error response for HTTP 404 Not Found.
2 properties 2 required
LinkObjectArray
array
List of links
LinkObject
object
2 properties 1 required
Decision
object
Records of manual approvals or rejections.
4 properties
CurrencyCode
string
Three-letter ISO 4217 currency code.
PaymentReference
string
The reconciliation reference that appears on the bank statement. This is crucial for matching the transaction with external banking records. Maximum length: 35…
PayoutTransactionRequest
object
7 properties 5 required
SettlementTransactionRequest
object
7 properties 5 required
OutgoingTransactionRequestBeneficiaryTrustedAccount
object
1 property 1 required
CountryCode
string
Alpha-2 country code
Error415Response
object
Request contains data in an unsupported content type.
2 properties 2 required
Address
object
Physical address of the beneficiary or sender.
5 properties
ValidationErrorDetail
object
Details about a specific validation error.
3 properties
XVoltTestingScenario
string
TransactionLinks
object
8 properties
Error406Response
object
API is not able to generate a response in the format defined in the Accept HTTP request header.
2 properties 2 required
RefundTransactionRequest
object
7 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

volt-io-transactions-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 Named Accounts API
Volt Sandbox API
Volt Trusted accounts API
Where this information came from

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