approveWalletLink
https://docs.hazbase.com/en/reference/http/approveWalletLink/

HTTP API / WALLET CLIENT
 approveWalletLink
 Inspect HTTP routes, arguments and responses used by @hazbase/kit/wallet. Additional authentication and passkey APIs are covered in the auth SDK reference and integration guide.
 https://api.hazbase.com @hazbase/kit 0.9.0 JSON 
 User-session, signature and permission requirements differ by API. Check the specifications below and the connection requirements of your API environment. Check API access requirements 
 ← HTTP API index 
 POST /api/wallet/link/approve 
 Request
 @hazbase/kit/wallet 
 approveWalletLink ( input : ApproveWalletLinkInput ) : Promise < ApproveWalletLinkResult > 

 emailSession is sent as an Authorization: Bearer header.
 Field Type Required Location 
 emailSession string Yes Authorization header 
 challengeId string Yes JSON body 
 nonce string Yes JSON body 
 walletAddress string Yes JSON body 
 chainId number Yes JSON body 
 endpoint string No SDK endpoint override 

 POST requests include Content-Type: application/json and x-request-id. The request ID supports tracking; it is not a blanket idempotency guarantee.

 Response
 typescript 
 1
2
3
4
5
6
 export type ApproveWalletLinkResult = { 
 challengeId : string ; 
 proof : string ; 
 expiresAt : string ; 
 status ? : string ; 
 } ; 

 Find nested types in the SDK reference. The client handles both a top-level response and a response wrapped in data.
 ApproveWalletLinkResult 
 Handling failures
 Non-2xx responses become HazbaseWalletApiError. Record status, code and message, distinguishing API errors from network failures. Keep credentials out of logs.
 Errors & troubleshooting 
 View source