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

HTTP API / WALLET CLIENT
 createWalletLinkChallenge
 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/challenge 
 Request
 @hazbase/kit/wallet 
 createWalletLinkChallenge ( input : CreateWalletLinkChallengeInput ) : Promise < WalletLinkChallengeResult > 

 This SDK method does not automatically add a Bearer header. Check any environment-level access requirements separately.
 Field Type Required Location 
 origin string Yes JSON body 
 purpose string No 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
7
8
 export type WalletLinkChallengeResult = { 
 challengeId : string ; 
 nonce : string ; 
 origin : string ; 
 purpose : 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.
 WalletLinkChallengeResult 
 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