Skip to main content
Authentication follows the challenge-response model (SIWS style). The application requests a challenge, signs it with the user’s wallet, and sends the signature to receive a JWT token.
The official SDK orchestrates the whole flow via client.auth.signIn(...). See Authentication and Configuration.

Request challenge

string
required
application/json
string
required
Wallet address that will authenticate.
string
required
Blockchain of the address (for example, solana).
string
Challenge message (nonce) to be signed by the wallet.

Verify signature

Sends the challenge signature and receives the JWT token.
string
required
application/json
string
required
Wallet address.
string
required
Blockchain of the address.
string
required
Challenge signature produced by the wallet.
string
JWT token to be used in the Authorization header of authenticated calls.

Send OTP

Sends a one-time password (OTP) as an additional factor, when applicable to the flow.
boolean
Indicates whether the code was sent successfully.

Token usage

Include the JWT token in the Authorization header of every authenticated call:
On 401 responses, sign in again. The SDK can automate this process with client.auth.enableAutoRelogin(...).