Send tokens

Fund your Wallet

Now that you have a wallet, the next step is to get test tokens for it. You can fund your wallet using the Fund wallet with testnet tokens Client API endpoint. If you are looking for a greater variety of test tokens, we recommend exploring our faucets page.

The chainId will need to be a CAIP-2 compliant Chain ID. For more info on Chain ID formatting, see this doc.

curl --request POST \
  --url https://api.portalhq.io/api/v3/clients/me/fund \
  --header 'Authorization: Bearer [clientApiKey|clientSessionToken]' \
  --header 'Content-Type: application/json' \
  --data '{
	"chainId": "eip155:10143",
	"token": "NATIVE",
	"amount": "0.01"
}'

Sending Tokens from your Wallet

Portal provides two ways to send transactions:

The Send Asset Enclave MPC API endpoint - Simply send tokens from your Portal wallet.
The Sign Enclave MPC API endpoint - Create and submit your own custom transactions from your Portal wallet.

For most use cases, we recommend using the Send Asset Enclave MPC API endpoint as shown in the examples below.

amount is the figure a wallet displays, in the token’s primary denomination. If your ledger is kept in base units (wei, lamports, satoshis), pass rawAmount instead: a positive integer string that moves on chain exactly as given, with no decimals or multiplier conversion. Send one or the other, not both.

EVM
Solana
Bitcoin
Tron

The below example sends 0.0001 ETH on Monad Testnet from your Portal client’s wallet.

curl --request POST \
  --url https://mpc-client.portalhq.io/v1/assets/send \
  --header 'Authorization: Bearer [clientApiKey|clientSessionToken]' \
  --header 'Content-Type: application/json' \
  --data '{
	"share": "SECP256K1.share",
	"rpcUrl": "https://api.portalhq.io/rpc/v1/eip155/10143",
	"chain": "monad-testnet",
	"to": "0xDestinationAddress",
	"token": "NATIVE",
	"amount": ".0001"
}'

The below example sends 0.0001 SOL on Solana Devnet from your Portal client’s wallet.

You will need SOL to submit a Solana transaction, which is not currently supported by POST /api/v3/clients/me/fund. You can find a faucet to get test SOL tokens here.

Scaled Token-2022 mints. Some Token-2022 mints display balances scaled from what they hold on chain: the ScaledUiAmount extension applies a multiplier set by the issuer, and the InterestBearing extension compounds a rate. Wallets and explorers show the scaled figure. Pass amount as that displayed figure. Portal converts it to base units with the mint’s decimals and then divides by the current multiplier to get the raw units that move on chain; metadata.rawAmount in the response is that raw figure and metadata.uiAmountMultiplier is the multiplier.

curl --request POST \
  --url https://mpc-client.portalhq.io/v1/assets/send \
  --header 'Authorization: Bearer [clientApiKey|clientSessionToken]' \
  --header 'Content-Type: application/json' \
  --data '{
	"share": "ED25519.share",
	"rpcUrl": "https://api.portalhq.io/rpc/v1/solana/EtWTRABZaYq6iMfeYKouRu166VU2xqa1",
	"chain": "solana-devnet",
	"to": "0xDestinationAddress",
	"token": "NATIVE",
	"amount": ".0001"
}'

The below example sends 0.0001 BTC on Bitcoin Testnet from your Portal client’s p2wpkh wallet.

You will need BTC to submit a Solana transaction, which is not currently supported by POST /api/v3/clients/me/fund. You can find a faucet to get test BTC tokens here.

The chain request body parameter for sending BTC can be one of:

bitcoin-segwit - The Portal client’s P2WPKH address on Bitcoin mainnet.
bitcoin-p2wpkh - The Portal client’s P2WPKH address on Bitcoin mainnet.
bitcoin-segwit-testnet - The Portal client’s P2WPKH address on Bitcoin testnet.
bitcoin-p2wpkh-testnet - The Portal client’s P2WPKH address on Bitcoin testnet.

curl --request POST \
  --url https://mpc-client.portalhq.io/v1/assets/send \
  --header 'Authorization: Bearer [clientApiKey|clientSessionToken]' \
  --header 'Content-Type: application/json' \
  --data '{
	"share": "SECP256K1.share",
	"chain": "bitcoin-segwit-testnet",
	"to": "tb1qDestinationAddress",
	"token": "NATIVE",
	"amount": ".0001"
}'

The below example sends 1 USDT on Tron Shasta Testnet from your Portal client’s wallet.

You can fund your wallet with TRX and USDT on Tron Nile (tron:nile) and Tron Shasta (tron:shasta) using POST /api/v3/clients/me/fund. Request TRX as well as USDT, since a USDT transfer needs TRX to pay for the transaction. You can also find Tron faucets here.

curl --request POST \
  --url https://api.portalhq.io/api/v3/clients/me/fund \
  --header 'Authorization: Bearer [clientApiKey|clientSessionToken]' \
  --header 'Content-Type: application/json' \
  --data '{
	"chainId": "tron:shasta",
	"token": "NATIVE",
	"amount": "50"
}'

On Tron, token can be NATIVE (TRX), USDT, or the USDT contract address for that network. Other TRC-20 tokens are not supported. A USDT transfer also needs TRX in the wallet to pay for the transaction.

Set rpcUrl to Portal’s RPC gateway for the network (https://api.portalhq.io/rpc/v1/tron/mainnet, .../tron/nile or .../tron/shasta), or to a gRPC address with an API key, such as grpc.trongrid.io:50051?api_key=<API_KEY>. Other HTTP(S) URLs are not supported for Tron, because Tron transactions are broadcast over gRPC.

curl --request POST \
  --url https://mpc-client.portalhq.io/v1/assets/send \
  --header 'Authorization: Bearer [clientApiKey|clientSessionToken]' \
  --header 'Content-Type: application/json' \
  --data '{
	"share": "SECP256K1.share",
	"rpcUrl": "https://api.portalhq.io/rpc/v1/tron/shasta",
	"chain": "tron:shasta",
	"to": "TDestinationAddress",
	"token": "USDT",
	"amount": "1"
}'

You just sent your first token from your Portal wallet, that’s awesome! 🎉

Account Abstraction clients (EVM sends): for an EVM send, the transactionHash returned by POST /v1/assets/send is a UserOperation hash, not an on-chain transaction hash — it will not resolve on a block explorer such as Etherscan or Monadscan. The on-chain transaction hash is only assigned once the bundler includes the UserOperation on-chain. Look up the UserOperation hash on a UserOp explorer such as JiffyScan to find the resulting transaction hash. Account Abstraction is EVM-only — Solana and Bitcoin sends return a normal on-chain transaction hash. See Account abstraction.

Advanced: Controlling Gas Sponsorship

If your client is using Account Abstraction, you can control whether Portal sponsors the gas fees for each transaction using the sponsorGas parameter.

Example: User Pays Gas

curl --request POST \
  --url https://mpc-client.portalhq.io/v1/assets/send \
  --header 'Authorization: Bearer [clientApiKey|clientSessionToken]' \
  --header 'Content-Type: application/json' \
  --data '{
    "share": "SECP256K1.share",
    "chain": "sepolia",
    "to": "0xDestinationAddress",
    "token": "NATIVE",
    "amount": "0.0001",
    "rpcUrl": "https://api.portalhq.io/rpc/v1/eip155/11155111",
    "sponsorGas": false
  }'

By setting sponsorGas: false, the Portal client will pay for the transaction fees instead of having them sponsored. This is useful for testing or when you want users to pay for specific operations.

Omitting sponsorGas or setting it to true produces the same behavior - both will sponsor gas if your environment is configured for AA on that chain. Only sponsorGas: false changes the default behavior to disable sponsorship.

Learn more about gas sponsorship control in the Account Abstraction guide. You may have a more advanced use case than simply sending tokens from your Portal wallet. Next, we will dive into how to build your own custom transaction and also how to sign it.

Getting Started

SDKs

APIs

Integrations

Resources

Fund your Wallet

Sending Tokens from your Wallet

Advanced: Controlling Gas Sponsorship

Example: User Pays Gas

​Fund your Wallet

​Sending Tokens from your Wallet

​Advanced: Controlling Gas Sponsorship

​Example: User Pays Gas

Fund your Wallet

Sending Tokens from your Wallet

Advanced: Controlling Gas Sponsorship

Example: User Pays Gas