Transaction API
Transaction API
AUTHORIZATION - Bearer Token
This folder is using Bearer Token
-------------------------------------------------------------------------------------------------
◾ Domain Code
TX Status
Signature Type
Transfer Method
◾ GET
---------------------------------------------------------------------------------------------------
Search - Recent withdrawal list
GET
https://apis.cubeapi.io/v1/wallets/{wid}/assets/transfers/recent
Path Parameters
Query Parameters
Search - ERC20 asset transfer history list
GET
https://apis.cubeapi.io/v1/wallets/{wid}/assets/transfers
Path Parameters
Query Parameters
Search - ERC20 asset transfer history detail V1
GET
https://apis.cubeapi.io/v1/wallets/{wid}/assets/transfers/{transferSeq}
Path Parameters
Query Parameters
Search - ERC20 asset transfer history detail V2
GET
https://apis.cubeapi.io/v2/wallets/{wid}/assets/transfers/{historySeq}
Lost of existing key uniqueness due to chain addition
Reset key for detail
Change trasferSeq -> historySeq
Path Parameters
Query Parameters
◾ POST
---------------------------------------------------------------------------------------------------
Check - Transfer Ticket V1
POST
https://apis.cubeapi.io/v1/transfers/estimate
Checking transfer availability and checking nonce, gas limit before generate transfer ticket(/v1/transfers/tickets)
Returns the WalletSignatureTicketDomain from which tickets can be generated
Ethereum transfer is possible from V2
Transacion Generation Flow
1.Cheking transfer ticket -> Checking readiness to send and return by adding required values for transfer
2.Generate transfer ticket -> Generate transfer history as ticket to save database and return ticket UUID
3.transfer transaction -> Through the ticket UUID and wallet passwords obtained by the generated transfer tickets, promote signature and network in server
Request Body
Check - Transfer Ticket V2
POST
https://apis.cubeapi.io/v2/transfers/estimate
Checking transfer availability and checking nonce, gas limit before generate transfer ticket(/v2/transfers/tickets)
Returns the WalletSignatureTicketDomain from which tickets can be generated
Transacion Generation Flow
1.Cheking transfer ticket -> Checking readiness to send and return by adding required values for transfer
2.Generate transfer ticket -> Generate transfer history as ticket to save database and return ticket UUID
3.transfer transaction -> Through the ticket UUID and wallet passwords obtained by the generated transfer tickets, promote signature and network in server
Request Body
Create - Transfer Ticket V1
POST
https://apis.cubeapi.io/v1/transfers/tickets
Transaction transfer process
1.Ticket create(/v1/transfers/ticksets)
2.Ticket authenfication(/v1/transfers/tickets/:ticketUuid)
Transaction authenfication - get HASH
transferHash + ${transferTo} + ${transferVal} + ${txInput} + ${contractAddress}
Headers
Create - Transfer Ticket V2
POST
https://apis.cubeapi.io/v2/transfers/tickets
Transaction transfer process
1.Ticket create(/v2/transfers/ticksets)
2.Ticket authenfication(/v2/transfers/tickets/:ticketUuid)
Transaction authenfication - get HASH
transferHash + ${transferTo} + ${transferVal} + ${txInput} + ${contractAddress}
Headers
Transfer - Transaction V2
POST
https://apis.cubeapi.io/v2/transfers/tickets/:ticketUuid
Batch Transaction available (Generate n transaction in one block)
Require pin encrypted with sha256