Retrieve execution inputs for a message
GET/messages/:messageId/execution-inputs
Retrieve the execution input data needed to execute a specific CCIP message. The response format depends on the lane version:
- Lane version 1.6 and below: Returns an array of encoded messages (all messages in the same commit batch as the desired one)
- Lane version 2.0+: Returns the encoded message along with verifier addresses, ccv data, and a
verificationCompleteboolean flag
For lane version 2.0+ messages:
- The endpoint always returns HTTP 200 with execution inputs, even if verification requirements are not yet satisfied
- Clients should check the
verificationCompletefield to determine if the message is ready for execution:true: All required verifiers and optional threshold met. Ready for execution.false: Verification requirements not yet satisfied. Additional verifications needed before execution.
Use Cases:
- Prepare data for message execution
Request
Responses
- 200
- 400
- 404
- 409
- 500
The request was successful. Returns execution input data in a format that depends on the lane version.
For lane version 1.6 and below, returns ExecutionInputsV1.
For lane version 2.0+, returns ExecutionInputsV2.
Response Headers
Unique request identifier for debugging and support
Bad request - Invalid message ID format. Returns an Error object.
Response Headers
Unique request identifier for debugging and support
Message not found. Returns an Error object.
Response Headers
Unique request identifier for debugging and support
Conflict - The message exists but execution inputs cannot be provided yet. This can occur when:
- The message has not been committed yet (no Merkle root available)
Retry the request later when the message has progressed further in its lifecycle.
Returns an Error object.
Response Headers
Unique request identifier for debugging and support
Internal server error. Returns an Error object.
Response Headers
Unique request identifier for debugging and support