​
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:11155111",
	"token": "NATIVE",
	"amount": "0.01"
}'

​
Sending Tokens from your Wallet

Portal provides two ways to send transactions:
  1. The Send Asset Enclave MPC API endpoint - Simply send tokens from your Portal wallet.
  2. 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.
The below example sends 0.0001 ETH on Ethereum Sepolia 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/11155111",
	"chain": "sepolia",
	"to": "0xDestinationAddress",
	"token": "NATIVE",
	"amount": ".0001"
}'
You just sent your first token from your Portal wallet, that’s awesome! 🎉 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.