Skip to content
    hazBasehazBaseDocs
    API accessGitHub
    GuidesQuickstartMCPSDKHTTP APIPatternsBUILD WITH hazBase
    HTTP API / WALLET CLIENT

    listTokens

    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

    GET /api/wallet/tokens

    Request

    @hazbase/kit/wallet
    listTokens(input: ListTokensInput = {}): Promise<ListTokensResult>
    This SDK method does not automatically add a Bearer header. Check any environment-level access requirements separately.
    FieldTypeRequiredLocation
    chainIdnumberNoQuery string
    endpointstringNoSDK 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 ListTokensResult = {
  tokens: WalletTokenSummary[];
  status?: string;
};

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

    ListTokensResult

    Example

    bash
    curl --fail-with-body \
  "https://api.hazbase.com/api/wallet/tokens?chainId=11155111" \
  -H "Accept: application/json"

    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