Deposit into a vault from a Smart Account
Deposits the vault’s underlying asset (e.g. USDC) from an end user’s EVM Smart Account into a vault. The token approval and deposit are batched into a single user operation, whose hash is returned in userOpHash.
Because the approval and deposit execute atomically in a single user operation, no share-price guard is required.
Poll getUserOperationWithEndUserAccount until the user operation reaches a terminal status.
For deposits from EOA accounts, use depositToVaultWithEndUserAccount instead.
The amount field accepts human-readable amounts as decimal strings (e.g., “1.5”, “25.50”) in the standard unit denomination of the vault’s underlying asset.
Authorizations
Headers
A JWT signed using your Wallet Secret, encoded in base64. Refer to the Generate Wallet Token section of our Authentication docs for more details on how to generate your Wallet Token.
Path Parameters
Query Parameters
Body
A request to deposit the vault's underlying asset (e.g. USDC) into a vault from an end user's EVM Smart Account. The token approval and deposit are batched into a single user operation.
Optional custom Paymaster URL to use for gas sponsorship. This allows you to use your own Paymaster service instead of CDP's Paymaster. Cannot be used together with useCdpPaymaster.
11 - 2048^https?://.*$"https://api.developer.coinbase.com/rpc/v1/base/AbCdEf123456"
The ERC-7677 context object forwarded to the paymaster service as part of the paymasterService capability. The fields in this object are defined by the paymaster service provider; CDP forwards them to the paymaster unchanged. This field is only valid when a paymaster is configured for the request. Providing paymasterContext without a paymaster configured results in an invalid_request error.
Response
Successfully broadcast the deposit user operation. Poll getUserOperationWithEndUserAccount for its status.