Introduction
The Volet.com Merchant API lets your application accept crypto payments, send payouts and transfers, track transactions, and read account information, such as balances, tariffs, and limits.
For step-by-step scenarios, see the guides: API integration for accepting payments and API integration for mass payouts.
Base URL
https://api.volet.com
All endpoints are relative to this URL, for example https://api.volet.com/api/account/balances.
Before you start
- A verified Volet.com account, personal or business.
- An API created in the Payment Tools section of your account, with the permissions your integration needs. See Create payment gateway or Enable mass payouts.
- The IP addresses of your servers on the IP whitelist of the API.
Volet.com does not offer a sandbox. Test your integration with small live transactions.
Authentication
Each request includes three headers:
| Header | Value |
|---|---|
Api-Name | The name of the API in your Volet.com account |
Account-Email | The email address of the Volet.com account that owns the API |
Authentication-Token | A SHA-256 token generated from your API password and the current UTC date and hour |
Generate the authentication token
- Build the string
password:YYYYMMDD:HH, wherepasswordis your API password, and the date and hour are in UTC. - Calculate the SHA-256 hash of the string.
- Send the hash as a hexadecimal string in the
Authentication-Tokenheader. The API does not check the letter case; lowercase is the usual form.
For example, for the password MySecret123 at 14:00 UTC on 26 October 2026:
SHA256("MySecret123:20261026:14")
produces:
c98e6521afe72b0945d9fdefdf3fd0b4dea10baa7f69325a7d6381c15f2421fd
The token changes every UTC hour. Generate it immediately before each request. The API also accepts the tokens of the previous and the next hour, so a request sent at the turn of the hour or from a server with a slightly wrong clock is not rejected.
In the Try it panel of each method, you can enter your API password and generate the token in your browser. The password is not sent anywhere.
Only the token is sent to the API, never the password. Do not put the API password or tokens in frontend code, mobile apps, bots, or other client-side scripts.
Request format
- Requests and responses use JSON over HTTPS. Send
Content-Type: application/jsonwith request bodies. - Amounts are decimal numbers, for example
"amount": 100. The API also accepts them as strings, such as"amount": "100.00". The number of decimal places depends on the currency. - Stablecoin codes include the network where funds move on a blockchain, for example
USDT_TRC20; wallet currencies are plain, such asUSDT. See Currency codes and amounts.
Example request:
curl https://api.volet.com/api/account/balances \
-H "Api-Name: my-api" \
-H "Authentication-Token: c98e6521afe72b0945d9fdefdf3fd0b4dea10baa7f69325a7d6381c15f2421fd"
Request limits
For personal accounts and for business accounts that have not completed verification, the API limits the number of requests per hour. When the limit is used up, the API returns HTTP 401 with the error attemptsHaveEndedException. Wait and send the request later. Verified business accounts do not have this hourly limit.
Related
- Get wallet balances — a simple first request to check your authentication
- API integration for accepting payments — crypto invoices, statuses, and notifications
- API integration for mass payouts — validating and sending payouts