Wallets

Pregenerate Wallets

Create wallets for users before they authenticate, enabling smoother onboarding and pre-funded asset distribution.

Use Cases

Pre-assign wallets to users before signup
Reduce onboarding time by eliminating wallet creation delays
Pre-fund wallets with tokens or NFTs before users claim them
Create smooth experiences for gaming and app onboarding
Distribute assets like game items, welcome bonuses, or promotional NFTs

API Reference

Request

POST


fetch("https://api.thirdweb.com/v1/wallets/user", {
  method: "POST",
  headers: {
    "x-secret-key": "<your-project-secret-key>",
  },
  body: {
    type: "email",
    email: "test@test.com",
  },
});

Response


{
  "result": {
    "address": "string",
    "profiles": [
      {
        "email": "string",
        "emailVerified": true,
        "hd": "string",
        "id": "string",
        "locale": "string",
        "picture": "string",
        "type": "google",
        "familyName": "string",
        "givenName": "string",
        "name": "string"
      }
    ],
    "createdAt": "string",
    "smartWalletAddress": "string",
    "publicKey": "string"
  }
}

Ecosystem Requirements

For ecosystem wallets, the secret key must be from the same account as the ecosystem owner.

Smart Wallet Addresses

The API returns the EOA (admin wallet) address. Use predictSmartAccountAddress to get the corresponding smart contract wallet address.

Next Steps

Pregeneration doesn't change the user experience. Users can login normally and will automatically receive their pregenerated wallet.

For more information, see the User Wallets documentation.