Namespace Thirdweb.Api
Classes
- Accounts
Account metadata required for executing an instruction.
- Actions
Sign a transaction
- Body10
Contract deployment specification for raw bytecode deployment.
- Body13
Request object containing an array of encoded blockchain transactions to execute. All transactions must use the same from address and chainId. For contract calls, use /v1/contracts/write. For native token transfers, use /v1/wallets/send.
- Body14
Request to create a product to be purchased. Users can purchase the product via hosted UI (link is returned), a transaction execution referencing the product ID, or embedded widgets with the product ID.
- Body15
Request to purchase a product. The system will automatically use your wallet balance to purchase the specified product.
- Body16
Request body for x402 facilitator 'verify'
- Body17
Request body for x402 facilitator 'settle'
- Body19
Request schema for creating a new ERC20 token
- Body20
Request to swap tokens using the optimal route available. You can specify a tokenIn amount (if exact='input') or tokenOut amount (if exact='output'), but not both. The corresponding output or input amount will be returned as the quote.
- Body21
Request payload for creating or fetching a Solana wallet by label.
- Body22
Request payload for signing an arbitrary Solana message.
- Body23
Request payload for signing a Solana transaction. Provide a serialized transaction or a set of instructions to be assembled server-side.
- Body24
Request payload for broadcasting a signed Solana transaction. Use the signedTransaction output from /v1/solana/sign-transaction.
- Body25
Request payload for transferring SOL or SPL tokens on Solana.
- Body26
Submit a Solana transaction made up of one or more instructions.
- Body27
Chat request
- Body3
Request body for linking an additional authentication method or external wallet to the currently authenticated user.
- Body4
Request body for unlinking an authentication provider or wallet from the currently authenticated user.
- Body5
Request body for pre-generating a wallet
- Body6
Request body for creating a wallet
- Body7
Request body for signing a message
- Body8
Request body for signing typed data
- Body9
Request body for sending tokens to multiple recipients. Supports native tokens, ERC20, ERC721, and ERC1155 transfers based on the provided parameters.
- ChainId
Chain ID in CAIP-2 format (e.g., 'eip155:1' for Ethereum, 'solana:mainnet' for Solana). Also accepts legacy numeric IDs for EVM chains.
- ChainId2
The chain ID to use for the payment in CAIP-2 format. Supports EVM chains (e.g., 'eip155:1', 1) and Solana chains (e.g., 'solana:mainnet'). If not provided, the chain ID from the url's payment requirements will be used.
- ChainId3
Solana network to query. Choose either solana:mainnet or solana:devnet.
- Contracts
Contract details enriched with additional project information from the API server.
- Instructions
Single Solana instruction that will be included in a transaction.
- LinkedAccounts
Authentication provider details with type-based discrimination
- Method
The method to use, defaults to GET
- Profiles
Authentication provider details with type-based discrimination
- Profiles2
Authentication provider details with type-based discrimination
- Profiles3
Authentication provider details with type-based discrimination
- Profiles4
Authentication provider details with type-based discrimination
- Response2
Successful authentication response. Returns wallet address plus authentication tokens.
- Response21
Payment required response when user has insufficient funds. Contains a quote for completing the purchase.
- Response24
Contract metadata from the thirdweb contract metadata service.
- Response25
Contract ABI signatures in human-readable format. These signatures can be used directly with contract interaction methods.
- Response29
Payment required response when user has insufficient funds. Contains a quote for completing the purchase.
- Response3
Response returned after successfully linking an additional authentication provider. The response includes all linked profiles for the user.
- Response30
Successful payment creation response containing the payment ID and link to purchase the product
- Response32
Payment required response when user has insufficient funds. Contains a quote for completing the purchase.
- Response36
Response returned by x402 facilitator 'verify'
- Response37
Response returned by x402 facilitator 'settle'
- Response38
Supported payment kinds for this facilitator
- Response39
Payment required response when user has insufficient funds. Contains a quote for completing the purchase.
- Response4
Response returned after successfully linking an additional authentication provider. The response includes all linked profiles for the user.
- Response49
Successful token swap response containing executed transaction ID
- Response50
Payment required response when user has insufficient funds. Contains a quote for completing the purchase.
- Response63
Chat response
- Routes
Represents a supported bridge route between an origin and destination token.
- ThirdwebHttpClientWrapper
Wrapper class that adapts IThirdwebHttpClient to work with System.Net.Http.HttpClient expectations
- Transactions
A blockchain transaction with pre-encoded data payload. For contract calls, use /v1/contracts/write. For native token transfers, use /v1/wallets/send.
- Wallets2
Details for a Solana wallet in your project.
- accounts
Account metadata required for executing an instruction.
- instructions
Single Solana instruction that will be included in a transaction.
- linkedAccounts
Authentication provider details with type-based discrimination
- profiles
Authentication provider details with type-based discrimination
Structs
Enums
- From
The fiat currency symbol
- IncludeNative
Whether to include native tokens (e.g., ETH, MATIC) in the results (default: true).
- IncludeSpam
Whether to include tokens marked as spam (default: false).
- IncludeWithoutPrice
Whether to include tokens without price data (default: true).
- Metadata
Whether to include token metadata (default: true).
- Provider
The OAuth provider to use
- ResolveMetadataLinks
Whether to resolve metadata links to fetch additional token information (default: true).
- SortBy
Field to sort tokens by: 'balance' for token balance, 'token_address' for token address, 'token_price' for token price, 'usd_value' for USD value (default: usd_value).
- SortOrder
Sort order: 'asc' for ascending, 'desc' for descending
- SortOrder2
Sort order: 'asc' for ascending, 'desc' for descending (default: desc).
- SortOrder3
Sort order: 'asc' for ascending, 'desc' for descending
- SortOrder4
Sort order: 'asc' for ascending, 'desc' for descending