submitOwnerOperation
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.
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
POST /api/wallet/operation/submit
Request
submitOwnerOperation(input: SubmitOwnerOperationInput): Promise<SubmitOwnerOperationResult>Operation authorization requires deviceBindingId and highTrustToken.
| Field | Type | Required | Location |
|---|---|---|---|
chainId | number | Yes | JSON body |
account | string | Yes | JSON body |
policyKey | string | Yes | JSON body |
calls | OwnerOperationCall[] | Yes | JSON body |
grantToken | string | Yes | JSON body |
metadata | Record<string, unknown> | No | JSON body |
endpoint | string | No | SDK endpoint override |
emailSession | string | Yes | Authorization header |
deviceBindingId | string | Yes | JSON body |
highTrustToken | string | Yes | JSON body |
accountSalt | string | No | JSON body |
paymasterValiditySec | string | No | JSON body |
waitForReceipt | boolean | No | JSON body |
POST requests include Content-Type: application/json and x-request-id. The request ID supports tracking; it is not a blanket idempotency guarantee.
Response
export type SubmitOwnerOperationResult = {
chainId: number;
operation: PrepareOwnerOperationResult['operation'];
policy: PrepareOwnerOperationResult['policy'];
relayMode?: string;
bundlerRpcUrl?: string | null;
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.
SubmitOwnerOperationResultHandling failures
Non-2xx responses become HazbaseWalletApiError. Record status, code and message, distinguishing API errors from network failures. Keep credentials out of logs.
Errors & troubleshooting