HTTP API / WALLET CLIENT

verifyWalletLink

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.0JSON

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/verify`

Request

@hazbase/kit/wallet

verifyWalletLink(input: VerifyWalletLinkInput): Promise<VerifyWalletLinkResult>

This SDK method does not automatically add a Bearer header. Check any environment-level access requirements separately.

Field	Type	Required	Location
`challengeId`	`string`	Yes	JSON body
`nonce`	`string`	Yes	JSON body
`proof`	`string`	Yes	JSON body
`origin`	`string`	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

export type VerifyWalletLinkResult = {
  verified: true;
  walletAddress: string;
  chainId: number;
  origin: string;
  purpose: string;
  assurance: 'authenticated_wallet_session';
  expiresAt: string;
  linkSessionToken: string;
  linkSessionExpiresAt: string;
  status?: string;
};

Find nested types in the SDK reference. The client handles both a top-level response and a response wrapped in data.

VerifyWalletLinkResult

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