alchemy_requestPaymasterAndData
Requests gas coverage for a `UserOperation`.
<Warning title="To be deprecated">
Please use `alchemy_requestGasAndPaymasterAndData` instead.
While you can use `alchemy_requestPaymasterAndData` to request a paymaster signature, it's important to note that this function requires gas fields to be part of the `UserOperation` passed as a parameter. These gas fields are influenced by the response of this endpoint, creating a circular dependency.
To simplify this process, we introduced alchemy_requestGasAndPaymasterAndData. This function both estimates gas and provides signed `paymaster` and `paymasterData` fields, therefore resolving the circular dependency.
</Warning>
Path Parameters
apiKey
Request
This endpoint expects an object.
policyId
The Gas Manager policy ID or list of Gas Manager policy IDs.
entryPoint
The EntryPoint address the request should be sent through. This MUST be one of the EntryPoints returned by the supportedEntryPoints RPC call and match the version of the userOperation in the userOperation field.
userOperation
Test Partial UserOperation object, missing paymasterAndData and signature fields. This can be either a v0.6 or v0.7 userOperation, but MUST match the version of the EntryPoint at the address in the entryPoint field.
erc20Context
Erc20 context, required to enable users to pay gas with ERC-20 tokens.
webhookData
Additional data you can include in the request, such as proof of humanity, if you have enabled custom rules in your Gas Manager policy.
Response
The response object may be one of two types:
entrypointV06Response
entrypointV07Response
