Construction

Parse High-Level Construction Operations

PreprocessOperations is called to parse and validate high-level transaction construction operations into Rosetta operations. This endpoint allows the Rosetta implementation to handle operation parsing that might not be supported by local client-side parsers.

This endpoint is OPTIONAL and implementations can return HTTP 501 (Not Implemented) if they don't support this functionality.

The input format matches TransactionConstructOpInput used by chainstdio, and the output format matches the return values of ParseTransactionConstructOp to maintain compatibility with existing operation parsing workflows.

post/construction/preprocess-operations

Request body

network_identifierNetworkIdentifier required— unresolved $ref
from_addressstring

The address that will be the source of the transaction. This is optional and may not be required for all construct operations.

construct_opstring required

The high-level operation type to be parsed (e.g. "transfer", "stake", "delegate").

optionsobject

Operation-specific parameters as a JSON object. The format of this object is specific to the construct_op type and the blockchain implementation.

Response

Expected response to a valid request

operationsOperation[] required— unresolved $ref

The parsed operations that result from processing the construct_op.

max_feeAmount — unresolved $ref
metadatastring byte

Metadata as raw JSON bytes, matching ParseTransactionConstructOp return format for compatibility with existing workflows.

Changes