API v1
Activating the API
To use the API, you need to enable the API module in the "Modules" section.

API Settings
After activating the module, go to the "API" -> "Settings" section. Set your desired configurations:

API: • Disabled — API access is restricted • All users — API access will be available to all users of the exchange • Selected users — API access will only be granted to users who have the "Work with REST API" option enabled in their user settings in the admin panel.

Logs — Log entries for API usage can be found in the "API" -> "Logs" section • No • Yes
Methods available to users — A set of methods that will be accessible to the user when adding a key in their personal account on the exchange.

Obtaining API Keys through the User's Personal Account
Users can access the API through their personal account, typically at the link https://your_domain/user-api/.

After selecting the methods and specifying the IP addresses, click the "Add API Key" button. The page will then display the generated pair of "Login — Key".

You can generate multiple keys for a single user with different sets of methods.
Creating API Keys through the Admin Panel
We recommend creating API keys specifically for individual users, rather than using the "System" user.
When you issue access under "System," you are granting access as the admin of the exchange — it's better to create API keys for the intended user. Otherwise, the user may gain access to all requests made via the API through the get_exchanges method (if enabled), rather than just those made from their own account.
On the "API" -> "Add" page, add a new API user.

User — User ID from the exchange or 0 (for the "System" user)
Allowed IP addresses — IP addresses from which API access will be permitted
Available methods — A set of methods that the user can utilize
After saving the data, a pair of "Login — Key" will be generated.

Using the API
Endpoint: https://your_domain/api/userapi/v1/ + API method
For authorization, you need to send the following information in the headers of your API requests, which you obtained earlier in the "API" section:
API-LOGIN — API login
API-KEY — API key
API-LANG — forced use of the specified language (optional). Example: ru_RU, en_US.
All requests are sent using the POST method, and responses are returned in JSON format (GET requests are not used). Parameters are passed in the body of the request (not in the header).
Example of a request with parameter transmission from Postman and the response to the request:

API Methods:
test
A test method to check the API functionality.
Request parameters:
Response:
get_direction_currencies
Retrieve a list of currencies available for exchange.
Request parameters:
Response:
get_directions
Retrieve a list of exchange directions available for exchange.
Request parameters:
Response:
get_direction
Retrieve information about a specific exchange direction.
Request parameters:
Response:
get_calc
Calculator for amounts in the exchange direction.
Request parameters:
Response:
get_exchanges
Retrieve requests created with this key.
Request parameters:
Response:
create_bid
Create a request.
Request parameters:
Here’s a naturalistic English translation of the provided text:
Parameters for Exchange Request:
direction_id — ID of the exchange direction
partner_id — ID of the partner (optional parameter)
api_id — ID of the request in your system (optional parameter)
calc_amount — amount of the exchange
calc_action — classification of the amount:
1 — amount in the "Giving" currency
2 — amount in the "Receiving" currency
3 — amount in the "Giving" currency with a fee
4 — amount in the "Receiving" currency with a fee
callback_url — specify the URL to which the API will send a response when the status of the request changes. The response will be sent via POST method:
bid_id — ID of the request
account1 — from account
cfgive8 — name of the cardholder
account2 — to account
cf1-99 — custom fields
Examples of fields:
cf1 — First Name
cf2 — Middle Name
cf3 — Last Name
cf4 — Phone
cf5 — Skype
cf6 — E-mail
cf8 — Passport Number
cf10 — Region
cf11 — Telegram
Response:
url — link to the exchange page
id — ID of the request
hash — hash of the request
status — status of the request
status_title — title of the request status
psys_give — payment system for the "Giving" currency
psys_get — payment system for the "Receiving" currency
currency_code_give — currency code for "Giving"
currency_code_get — currency code for "Receiving"
amount_give — amount in the "Giving" currency
amount_get — amount in the "Receiving" currency
api_actions — options
type — type of payment
cancel — method for canceling the request
api — via API
disabled — disabled
link to cancel
pay — method of payment
api — via API
disabled — disabled
link to pay
instruction — payment instructions
pay_amount — amount to be paid
cancel_bid
Cancel a request (this method only works if, when creating the request (create_bid), the response api_actions -> cancel = 'api')
Request Parameters:
Response:
pay_bid
Mark the request as paid (this method works only if when creating the request via create_bid, the response contains "api_actions"-> "pay": "api" (when a merchant is not used in the exchange direction)).
_eng.png)
If a merchant was used in the request, the request will change its status to "Paid" only automatically (when the merchant sees the funds received for the request).
Request Parameters:
Response:
success_bid
Mark the request as completed.
Request Parameters:
Response:
_eng.png)
bid_info
Payment information about the request.
Warning: You can only request information about the request using this method if the request was created via the API.
Request Parameters:
Response:
get_partner_info
Information about the partner.
Request Parameters:
Response:
get_partner_links
Information about partner referrals.
Request Parameters:
Response:
get_partner_exchanges
Information about partner exchanges.
Request Parameters:
Response:
get_partner_payouts
List of user requests for fund withdrawals.
Request Parameters:
Response:
add_partner_payout
Create a payout request.
Request Parameters:
Response:
API Error Responses
Api disabled
_eng.png)
Possible reasons for the error and how to resolve them:
Incorrect authorization details provided in the "API" section for the user working with the API.
_eng.png)
API access not enabled in the user settings in the "Users" section.
_eng.png)
Empty Response
_eng.png)
Requested information is not available — check the parameters being sent.
No bid exists
_eng.png)
The requested bid does not exist.
Method not supported
_eng.png)
The selected method is not activated in the "API" section for the user.
_eng.png)
Direction not found
_eng.png)
Access to the exchange direction via the API is not allowed (when requesting the exchange direction); access must be enabled in the settings of the exchange direction, under the "Restrictions and Checks" tab.
_eng.png)
This translation aims to maintain clarity and readability while accurately conveying the original content's meaning.
Last updated