---
title: "Send Arbitrum from a virtual account to the blockchain"
method: POST
path: "/v3/offchain/arb/transfer"
tags: ["Blockchain operations"]
---

# Send Arbitrum from a virtual account to the blockchain

`POST /v3/offchain/arb/transfer`

## Request

- Base URL: `https://api.tatum.io`
- URL: `https://api.tatum.io/v3/offchain/arb/transfer`
- Auth: API key in header `x-api-key`

/v3/offchain/arb/transfer

**4 credits per API call**

Send ETH\_ARB or ERC-20-equivalent Arbitrum tokens from a virtual account (even from a virtual account without deposit addresses adssigned) to the Arbitrum blockchain.

The recipient has to agree in advance to receive assets because Arbitrum charges users for storing assets on their addresses, and an Arbitrum blockchain address by default does not receive assets unless explicitly agreed. Before sending any asset from a virtual account to the blockchain, make sure that the recipient [has agreed to receive the assets](https://apidoc.tatum.io/tag/Arbitrum#operation/ArbitrumBlockchainReceiveAsset) to their address.

Sending Arbitrum assets creates an internal Tatum withdrawal request with an ID. If everything works as expected, the withdrawal request is marked as complete and a transaction ID is assigned to it.

*   If a server connection is unavailable, the withdrawal request is cancelled.
*   If the transfer to the blockchain is successful, but the Tatum infrastructure cannot be accesses, the ID of the blockchain transaction is returned and you have to [complete the withdrawal request manually](https://apidoc.tatum.io/tag/Withdrawal#operation/completeWithdrawal). Otherwise, all other withdrawals will be pending.

**Signing a transaction**  
When sending ETH\_ARB or ERC-20-equivalent Arbitrum tokens, you are charged a fee for the transaction, and you must sign the transaction with the private key of the blockchain address from which the fee will be deducted.

Providing the private key in the API is not a secure way of signing transactions, because the private key can be stolen or exposed. Your private keys should never leave your security perimeter. You should use the private keys only for testing a solution you are building on the **testnet** of a blockchain.

## Request body

- union
  - TransferEth
    - `nonce` number: The nonce to be set to the transaction; if not present, the last known nonce will be used
    - `address` string, required: Blockchain address to send assets
    - `amount` string, required: Amount to be sent in Ether | MATIC | XDC | KCS.
    - `compliant` boolean: Compliance check, if withdrawal is not compliant, it will not be processed.
    - `privateKey` string, required: Private key of sender address. Either mnemonic and index, privateKey or signature Id must be present - depends on the type of account and xpub.
    - `paymentId` string: Identifier of the payment, shown for created Transaction within Tatum sender account.
    - `senderAccountId` string, required: Sender account ID
    - `senderNote` string: Note visible to owner of withdrawing account
    - `gasLimit` string: Gas limit for transaction in gas price. If not set, automatic calculation will be used.
    - `gasPrice` string: Gas price in Gwei. If not set, automatic calculation will be used.
  - TransferEthMnemonic
    - `nonce` number: The nonce to be set to the transaction; if not present, the last known nonce will be used
    - `address` string, required: Blockchain address to send assets
    - `amount` string, required: Amount to be sent in Ether | MATIC | XDC | KCS.
    - `compliant` boolean: Compliance check, if withdrawal is not compliant, it will not be processed.
    - `index` integer, required: Derivation index of sender address.
    - `gasLimit` string: Gas limit for transaction in gas price. If not set, automatic calculation will be used.
    - `gasPrice` string: Gas price in Gwei. If not set, automatic calculation will be used.
    - `mnemonic` string, required: Mnemonic to generate private key for sender address. Either mnemonic and index, privateKey or signature Id must be present - depends on the type of account and xpub.
    - `paymentId` string: Identifier of the payment, shown for created Transaction within Tatum sender account.
    - `senderAccountId` string, required: Sender account ID
    - `senderNote` string: Note visible to owner of withdrawing account

## Response `200`

OK

- union
  - OffchainTransactionResult
    - `id` string, required: ID of withdrawal. If transaction is not valid in blockchain, use this id to cancel withdrawal.
    - `txId` string, required: TX hash of successful transaction.
    - `completed` boolean, required: If set to "true", the withdrawal has been completed in the virtual account; if set to "false", the withdrawal has not been completed and you have to <a href="https://apidoc.tatum.io/tag/Withdrawal#operation/completeWithdrawal" target="_blank">complete it manually</a>
  - OffchainTransactionSignatureResult
    - `signatureId` string, uuid, required: ID of prepared payment template to sign. This is should be stored on a client side to retrieve ID of the blockchain transaction, when signing application signs the transaction and broadcasts it to the blockchain.

## Other responses

- `400`: Bad Request
- `401`: Unauthorized. Not valid or inactive subscription key present in the HTTP Header.
- `403`: Forbidden. The request is authenticated, but it is not possible to required perform operation due to logical error or invalid permissions.
- `500`: Internal server error. There was an error on the server during the processing of the request.

---

[API](https://skmtc.dev/tatum/apis/virtual-accounts.md) - [All operations](https://skmtc.dev/tatum/apis/virtual-accounts/llms.txt) - [OpenAPI document](https://skmtc.dev/tatum/apis/virtual-accounts/revisions/ba220553084b?raw)