Before you can POST transactions, you need to have the following:
POST your & retrieve your bank account ID
POST your & retrieve your wallet ID
Get . Please note - if you get redirected to the home page, you are already KYC approved.
Introduction
Creating and managing transactions with the Octane Transactions API is a straightforward process:
Create Transaction (POST):
Use the /v2/octane/transactions endpoint.
Provide essential details like blockchain type, currency pairs, quantities, and associated wallet and bank account information in the request body. More on this below.
Results in successful order creation with timestamp and transaction type details.
Retrieve All Orders (GET):
Utilize the /v2/octane/transactions endpoint with a GET request.
Retrieve all orders linked to the provided apiKey.
Access detailed information such as IDs, blockchain specifics, currencies involved, and timestamps.
Upcoming filtering options allow you to refine results.
Retrieve Specific Order (GET):
Access details of a specific order using the /v2/octane/transactions/:id endpoint.
Provide the order's ID and apiKey.
Retrieve comprehensive details, including transaction types, completion status, and precise currency exchange specifics.
Transactions API Endpoints
Post Transaction
POSThttps://api.abyiss.com/v2/octane/transactions
Returns a 201 status code upon successful query. Then returns the successful order. Requires user to have associated bank account and wallet.
Headers
Name
Type
Description
apiKey*
string
Blockchain ID
Request Body
The transaction request object is broken up into two levels. The top-level transaction request object contains the three fields in the following table. The second level contains the information inside the sourceOrder and destinationOrder objects.
Top Level Transaction Field Name
Type
Description
settlementMethod*
string
How the fiat-side of the transaction will be settled.
sourceOrder*
object
Information about where you are sending the currency from.
destinationOrder*
object
Information about where you are sending the currency to.
Order Field Name
Type
Description
walletId*
string
The user's wallet ID associated with the order.
blockchain*
string
Blockchain used for the order.
currency*
string
Currency of the order.
quantity*
string
Quantity of the currency in the order.
bankAccountId*
string
The user's bank ID which the fiat will be sent or received.
{
"errors": [{
"message": "Forbidden: Account is not KYC/KYB verified. Please contact support@abyiss.com"
}],
"code": 403
}
Transaction Customization
Selecting a Settlement Method
Abyiss supports ACH and WIRE as settlement methods. You can select the settlement method by providing one of the othe former values in the transaction.settlementMethod field. Please note that for on ramping, we only support WIRE transactions. This means that if you would like to buy crypto with a fiat currency, you must send Abyiss a wire transfer. For off ramping, we support both ACH and WIRE transactions. This means that if you would like to sell crypto for a fiat currency, you can choose to receive USD directly in your bank account via either WIRE or ACH.
WIRES
Wires cost $25 when OFF RAMPing. We do not charge for WIRES when ON RAMPing, however, your bank may charge you a wire fee.
When off ramping via wire, you will receive your funds in your bank account within 1-2 business days. Often times, you will receive your funds the same day that we send them. Please note that since Abyiss is a US-based company, we only send wires during US business hours. This means that if you request a wire after 5 PM EST, it will most likely be sent the next business day.
ACH
ACH transactions are completely free on the Abyiss network. ACH transactions can take 2-5 business days to settle. ACH transactions are only available for off ramping. This means that if you would like to sell crypto for a fiat currency, you can choose to receive USD directly in your bank account via ACH.
Selecting a Blockchain
Please ensure that when selecting a blockchain, that you are using a wallet address that has been registered to that blockchain. For example, if you are using the Ethereum blockchain, you must use an Ethereum wallet address. If you are using the Avalanche blockchain, you must use an Avalanche wallet address. For wallet addresses that are usable across multiple blockchains, you must register the wallet address to each blockchain that you would like to use it with.
Off Ramp Transaction
Off ramp transactions are inferred from the request. If the source order contains wallet and blockchain information and the destination order contains bank account information, then the transaction is an off-ramp transaction. Off ramp transactions may be settled in your bank account via ACH or WIRE.
On Ramp Transaction
On ramp transactions are inferred from the request. If the source order contains bank account information and the destination order contains wallet and blockchain information, then the transaction is an on-ramp transaction. On ramp transactions are settled directly in your wallet.
Get Transactions
GEThttps://api.abyiss.com/v2/octane/transactions
Returns an array of all the orders for an associated apiKey.
import requests
url = 'https://api.abyiss.com/v2/octane/transactions?apiKey=YOUR_API_KEY_HERE'
response = requests.get(url)
print(response.status_code) # This will print the status code of the response
print(response.json()) # This will print the response content as JSON
const url = 'https://api.abyiss.com/v2/octane/transactions?apiKey=YOUR_API_KEY_HERE';
fetch(url)
.then(response => {
if (!response.ok) {
throw new Error('Network response was not ok');
}
return response.json();
})
.then(data => {
console.log(data); // Handle the response data
})
.catch(error => {
console.error('There has been a problem with your fetch operation:', error);
});
Timestamp indicating when the transaction was created.
flaggedAt
string
Timestamp indicating when the transaction was flagged (if applicable).
completedAt
string
Timestamp indicating when the transaction was completed.
updatedAt
string
Timestamp indicating when the transaction was last updated
sellOrder
object
Information about the sell order.
buyOrder
object
Information about the buy order.
id
string
Unique identifier for the order.
bankAccountId
string
ID of the bank account associated with the order.
blockchain
string
Blockchain used for the order.
createdAt
string
Timestamp indicating when the order was created.
currency
string
Currency to be sold or bought.
feeUsd
string
Fee in USD for the order.
priceUsd
string
Price in USD for the order.
quantity
string
Quantity of the currency to be bought or sold.
updatedAt
string
Timestamp indicating when the order was last updated.
walletId
string
ID of the wallet associated with the order.
The sourceOrder and the Destination Order are identical in structure. It is worth noting that not all fields are required for each destination and source order. However, a combination of all fields are required amongst the entire transaction. Please reference for more information. The fields for source and destination order request objects are outlined below.
