Dev Platform: Server Wallets

Server wallet transaction flow

Overview

1Shot API wallets are Ethereum-compatible signing keys managed by 1Shot API to submit transactions on your behalf when you make a REST call to one of your configured contract methods.

Each wallet can be linked to one or more smart contract methods, while each contract method has only one default wallet. You can override the default wallet when calling the endpoint from your API integration.

To submit transactions from any 1Shot API-managed wallet, you must first deposit native gas tokens.

1Shot API's server wallet infrastructure is built on Google KMS.

When a wallet runs low on funds, 1Shot API automatically sends an email notification. Deposits also trigger a confirmation email when detected by the service. You can configure the low-balance threshold in the wallet details page.

Creating a Server Wallet

Navigate to Wallets in the 1Shot API dashboard.

Click Create Wallet, then enter a wallet name, description, and target blockchain network.

Funding Your Server Wallet

Deposit native gas tokens into your wallet so it can pay for transactions signed by that key.

Only fund the wallet with assets on the target blockchain the wallet is configured for.

• Ethereum mainnet wallet -> fund with mainnet ETH.
• Polygon wallet -> fund with Polygon native gas token (POL).

Withdrawing Funds

You can withdraw funds at any time from a wallet detail page by clicking Withdraw.

Enter the amount of native gas tokens to withdraw, click Send, and confirm the withdrawal details before submission.

Account Delegation

1Shot API supports EIP-7710 account delegation, which lets you delegate permissions from a self-custodied wallet to the 1Shot API service while keeping control of your private keys.

Delegation is performed through MetaMask Delegation Toolkit. When signing a delegation, you can define time bounds and allowed contract methods, cryptographically constraining what 1Shot API can execute on your behalf.