Wraps the Crypto Wallet Authenticate Start endpoint. Call this method to prompt the user to sign a challenge using their crypto wallet. For Ethereum crypto wallets, the challenge will follow the Sign In With Ethereum (SIWE) protocol if you have toggled SIWE Enabled in the SDK Configuration page . The domain and URI will be inferred automatically, but you may optionally override the URI. Load the challenge data by callingDocumentation Index
Fetch the complete documentation index at: https://stytch.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
cryptoWallets.authenticateStart(). You’ll then pass this challenge to the user’s wallet for signing. You can do so by using the crypto provider’s built-in API and by including the crypto_wallet_address and challenge that is provided from cryptoWallets.authenticateStart(). See Ethereum’s EIP-1193 for an example of Ethereum’s provider API.
Parameters
The type of wallet to authenticate. Currently ethereum and solana are supported. Wallets for any EVM-compatible chains (such as Polygon or BSC) are also supported and are grouped under the ethereum type.
The crypto wallet address to authenticate.
The parameters for a Sign In With Ethereum (SIWE) message. May only be passed if the crypto_wallet_type is ethereum and if you have toggled SIWE Enabled in the Frontend SDK page.
Response
A challenge string to be signed by the wallet in order to prove ownership.
Globally unique UUID that is returned with every API call. This value is important to log for debugging purposes; we
may ask for this value to help identify a specific API call when helping you debug an issue.
The HTTP status code of the response. Stytch follows standard HTTP response status code patterns, e.g. 2XX values
equate to success, 3XX values are redirects, 4XX are client errors, and 5XX are server errors.