Skip to main content

Retrieve #

Retrieve user information
CashewDaphne
#

Retrieve the information of the given user.

GET /v1/users/{userId}

Retrieve user wallet transaction history
CashewDaphne
#

Retrieve the transaction details related to the given user wallet. 'User wallet related transactions' should meet one of the following conditions.

GET /v1/users/{userId}/transactions
  1. Transactions signed and committed by the given user wallet
  2. Transactions generated by other wallets, containing the address of the given user wallet

Retrieve base coin balance (user wallet)
Cashew
#

Retrieve the balance of base coins in the given user wallet.

GET /v1/users/{userId}/base-coin

Retrieve balance of all service tokens (user wallet)
CashewDaphne
#

Retrieve the balance of all service tokens held by the given user.

GET /v1/users/{userId}/service-tokens

Retrieve balance of a specific service token (user wallet)
CashewDaphne
#

Retrieve the balance of a specific service token held by the given user.

GET /v1/users/{userId}/service-tokens/{contractId}

Retrieve balance of all fungibles (user wallet)
CashewDaphne
#

Retrieve the balance of all fungible item tokens held by the given user.

GET /v1/users/{userId}/item-tokens/{contractId}/fungibles

Retrieve balance of a specific fungible (user wallet)
CashewDaphne
#

Retrieve the balance of a specific fungible item token held by the given user.

GET /v1/users/{userId}/item-tokens/{contractId}/fungibles/{tokenType}

Retrieve balance of all non-fungibles (user wallet)
CashewDaphne
#

Retrieve the balance of all non-fungible item tokens held by the given user.

GET /v1/users/{userId}/item-tokens/{contractId}/non-fungibles

Retrieve balance of specific type of non-fungibles (user wallet)
CashewDaphne
#

Retrieve the balance of a specific non-fungible item token with the given Token Type held by the user.

GET /v1/users/{userId}/item-tokens/{contractId}/non-fungibles/{tokenType}

Retrieve balance of a specific non-fungible (user wallet)
CashewDaphne
#

Retrieve the balance of a specific non-fungible item token with the given Token Index held by the given user.

GET /v1/users/{userId}/item-tokens/{contractId}/non-fungibles/{tokenType}/{tokenIndex}

Retrieve the status of a session token
CashewDaphne
#

Retrieve the status of the session token issued by the given user wallet from LINE BITMAX Wallet.

GET /v1/user-requests/{requestSessionToken}

This endpoint can be used under the following situations.

  • Transferring base coin or service token from the user wallet.
  • Signing a transaction with the user wallet after obtaining service token and item token management permissions.

Retrieve whether the service token proxy set or not
CashewDaphne
#

Check if the proxy is set on the service token in the given user wallet.

GET /v1/users/{userId}/service-tokens/{contractId}/proxy

Retrieve whether the item token proxy set or not
CashewDaphne
#

Check if the proxy is set on a specific item token in the given user wallet.

GET /v1/users/{userId}/item-tokens/{contractId}/proxy

Issue #

Issue a session token for base coin transfer
Cashew
#

Issue a session token for LINE BITMAX Wallet passcode authentication to transfer base coins in the given user wallet to another wallet. A new session token should be issued for each transfer, and the same token can't be reused.

POST v1/users/{userId}/base-coin/request-transfer

You need to go through the following two steps to make a transfer.

  1. Call the Retrieve the status of a session token endpoint, using this session token as a parameter.
  2. When you receive "Authorized" as a response of Step 1, call the Commit a transaction signed by a user wallet endpoint, using this session token as a parameter.

Issue a session token for service token transfer
CashewDaphne
#

Issue a session token for LINE BITMAX Wallet passcode authentication to transfer service tokens in the given user wallet to another wallet.

POST /v1/users/{userId}/service-tokens/{contractId}/request-transfer

You need to go through the following two steps to make a transfer.

  1. Call the Retrieve the status of a session token endpoint, using this session token as a parameter.
  2. When you receive "Authorized" as a response of Step 1, call the Commit a transaction signed by a user wallet endpoint, using this session token as a parameter.

Issue a session token for service token proxy setting
CashewDaphne
#

Issue a session token for LINE BITMAX Wallet passcode authentication to set proxy with a specific service token in the given user wallet.

POST /v1/users/{userId}/service-tokens/{contractId}/request-proxy

Proxy is a service wallet that has permissions to transfer, and burn a service token in the user wallet through user authentication. When the proxy is set, the relevant permissions are delegated to the contract owner wallet that the given service token belongs to and this contract owner wallet can generate a transaction on behalf of the user wallet from then on. Other service wallets, except for the owner wallet, don't have permissions.

This endpoint issues a session token for setting a proxy only. You need to take two additional steps to complete proxy setup as follows.

  1. Call the Retrieve the status of a session token endpoint, using this session token as a parameter.
  2. When you receive "Authorized" as a response of Step 1, call the Commit a transaction signed by a user wallet endpoint, using this session token as a parameter.

Proxy setup for the given service token is performed only once per user. Once set, the proxy can’t be released.

Issue a session token for item token proxy setting
CashewDaphne
#

Issue a session token for LINE BITMAX Wallet passcode authentication to set the proxy for all item tokens of the given contract in the given user wallet.

POST /v1/users/{userId}/item-tokens/{contractId}/request-proxy

Proxy is a service wallet that has permissions to send, attach, detach, and burn an item token in the user wallet through user authentication. When the proxy is set, the relevant permissions are delegated to the contract owner wallet that the given item token belongs to and this contract owner wallet can generate a transaction on behalf of the user wallet from then on. Other service wallets, except for the owner wallet, don't have permissions.

This endpoint issues a session token for setting a proxy only. You need to take two additional steps to complete proxy setup as follows.

  1. Call the Retrieve the status of a session token endpoint, using this session token as a parameter.
  2. When you receive "Authorized" as a response of Step 1, call the Commit a transaction signed by a user wallet endpoint, using this session token as a parameter.

Proxy setup for all item tokens of the given contract is performed only once per user. Once set, the proxy can't be released.

Commit a transaction signed by a user wallet
CashewDaphne
#

Commit a transaction signed by the given user wallet.

POST /v1/user-requests/{requestSessionToken}/commit

Transfer #

Transfer a delegated service token (user wallet)
CashewDaphneRate limit & pricing
#

Request to transfer the delegated service token in the given user wallet to another wallet.

POST /v1/users/{userId}/service-tokens/{contractId}/transfer

When you're transferring a delegated service token from the user wallet, you should use the address and secret of the contract owner wallet for the service token, instead of the user wallet. To this end, you need to set up a proxy in the user wallet in advance. Refer to Issue a session token for service token proxy setting.

Transfer a delegated fungible (user wallet)
CashewDaphneRate limit & pricing
#

Request to transfer the delegated fungible item token in the given user wallet to another wallet.

POST /v1/users/{userId}/item-tokens/{contractId}/fungibles/{tokenType}/transfer

When you're transferring a delegated fungible item token from the user wallet, you should use the address and secret of the contract owner wallet for the given item token, instead of the user wallet. To this end, you need to set up a proxy in the user wallet in advance. Refer to Issue a session token for item token proxy setting.

Transfer a delegated non-fungible (user wallet)
CashewDaphneRate limit & pricing
#

Request to transfer the delegated non-fungible item token in the given user wallet to another wallet.

POST /v1/users/{userId}/item-tokens/{contractId}/non-fungibles/{tokenType}/{tokenIndex}/transfer

When you’re transferring a delegated non-fungible item token from the user wallet, you should use the address and secret key of the the contract owner wallet for the given non-fungible item token, instead of the user wallet. To this end, you need to set up a proxy in the user wallet in advance. Refer to Issue a session token for item token proxy setting.

Batch transfer delegated non-fungibles (user wallet)
CashewDaphneRate limit & pricing
#

Request to batch transfer multiple delegated non-fungible item tokens in the given user wallet to another wallet.

POST /v1/users/{userId}/item-tokens/{contractId}/non-fungibles/batch-transfer

Item tokens that are batch transferred must belong to the same contract, and they should be sent to the single wallet each time.

When you’re transferring multiple delegated non-fungible item token from the user wallet, you should use the address and secret key of the the contract owner wallet for the given non-fungible item token, instead of the user wallet. To this end, you need to set up a proxy in the user wallet in advance. Refer to Issue a session token for item token proxy setting.

Last updated on