This operation signs a message using the specified wallet via the Cobo WaaS platform. Currently supports EIP-712 structured data signing, with future support planned for raw hash signing, BTC signatures, and other schemes.
Set destination_type to select the signing method:
eip712 (default): EIP-712 typed structured data signing. Requires an EVM-compatible chain and the eip712_typed_data payload field.Set sync=true (default) to wait synchronously for the signing result before responding. Set sync=false to return immediately after submission; poll the transaction record to retrieve the signature later.
Supply request_id to enable idempotency. If a message-sign transaction with the same request_id already exists for the same principal, the existing record is returned with idempotent=true.
The operation returns an error if a policy denies the signing request.
The UUID of the wallet that will sign the message. Retrieve this value from the id field returned when the wallet was created.
Request payload for message signing.
Currently supports EIP-712 structured data signing.
The destination_type field determines which payload field is required.
CAW/WaaS chain ID, e.g. 'ETH', 'SETH'
Signing type. Determines which payload field is used.
eip712 Complete EIP-712 typed data: {domain, types, primaryType, message}. Required when destination_type='eip712'.
Specific address to sign with. If omitted, the wallet's most recently created address for this chain is used.
512True: wait for signature before responding. False: return immediately after submit.
Idempotency key. Replays are scoped to the same principal.
255Successful Response
Response for message signing.
Pagination metadata for list responses.
Supports both legacy offset-based and cursor-based pagination.
Cursor fields (has_more, after, before) are populated for
cursor-paginated endpoints. Legacy fields (offset, limit) are
populated when the caller uses the deprecated offset parameter.