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

    submitTransfer

    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/submit

    Request

    @hazbase/kit/wallet
    submitTransfer(input: SubmitTransferInput): Promise<SubmitTransferResult>
    emailSession is sent as an Authorization: Bearer header.

    Operation authorization requires deviceBindingId and highTrustToken.

    FieldTypeRequiredLocation
    emailSessionstringYesAuthorization header
    chainIdnumberNoJSON body
    tokenstringYesJSON body
    accountstringYesJSON body
    recipientstringYesJSON body
    amountstringYesJSON body
    deviceBindingIdstringYesJSON body
    highTrustTokenstringYesJSON body
    accountSaltstringNoJSON body
    paymasterValiditySecnumberNoJSON body
    waitForReceiptbooleanNoJSON body
    metadataRecord<string, unknown>NoJSON body
    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 SubmitTransferResult = {
  chainId: number;
  token: WalletTokenSummary;
  transfer: {
    account: string;
    recipient: string;
    amount: PrepareTransferResult['amount'];
    execution: PrepareTransferResult['execution'];
  };
  relayMode?: string;
  bundlerRpcUrl?: string;
  entryPointAddress?: string;
  smartAccountAddress: string;
  nonce: string;
  initCode: string;
  localUserOpHash?: string | null;
  submittedUserOpHash?: string | null;
  transactionHash?: string | null;
  gasEstimate?: Record<string, unknown>;
  receipt?: Record<string, unknown> | null;
  metadata?: Record<string, unknown>;
  status?: string;
};

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

    SubmitTransferResult

    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