submitTransfer
https://docs.hazbase.com/en/reference/http/submitTransfer/

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

 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 
 deviceBindingId string Yes JSON body 
 highTrustToken string Yes JSON body 
 accountSalt string No JSON body 
 paymasterValiditySec number No JSON body 
 waitForReceipt boolean 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 
 1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
 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