HTTP API / WALLET CLIENT

getTransferStatus

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/transfer/status`

Request

@hazbase/kit/wallet

getTransferStatus(input: GetTransferStatusInput): Promise<GetTransferStatusResult>

emailSession is sent as an Authorization: Bearer header.

Field	Type	Required	Location
`emailSession`	`string`	Yes	Authorization header
`chainId`	`number`	No	JSON body
`token`	`string`	Yes	JSON body
`account`	`string`	Yes	JSON body
`recipient`	`string`	Yes	JSON body
`amount`	`string`	Yes	JSON body
`userOpHash`	`string`	Yes	JSON body
`transactionHash`	`string`	No	JSON body
`relayMode`	`string`	No	JSON body
`metadata`	`Record<string, unknown>`	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 GetTransferStatusResult = {
  chainId: number;
  token: WalletTokenSummary;
  account: string;
  recipient: string;
  amount: PrepareTransferResult['amount'];
  submittedUserOpHash: string;
  transactionHash?: string | null;
  confirmed: boolean;
  blockNumber?: number;
  logIndex?: number;
  retryAfterMs?: number;
  errorCode?: string;
  status: string;
};

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

GetTransferStatusResult

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