HTTP API / WALLET CLIENT

getActivity

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

Request

@hazbase/kit/wallet

getActivity(input: GetActivityInput): Promise<GetActivityResult>

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

Field	Type	Required	Location
`chainId`	`number`	No	JSON body
`token`	`string`	Yes	JSON body
`account`	`string`	Yes	JSON body
`limit`	`number`	No	JSON body
`cursor`	`string`	No	JSON body
`fromBlock`	`number`	No	JSON body
`toBlock`	`number`	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

export type GetActivityResult = {
  chainId: number;
  account: string;
  token: WalletTokenSummary;
  activities: WalletActivityItem[];
  nextCursor?: string | null;
  range?: {
    fromBlock: number;
    toBlock: number;
    latestBlock: number;
  };
  status?: string;
};

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

GetActivityResult

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