Skip to main content
POST
/
v2
/
tokenized_assets
/
order
/
submit
Python (SDK)
from compass_api_sdk import CompassAPI


with CompassAPI(
    api_key_auth="<YOUR_API_KEY_HERE>",
) as compass_api:

    res = compass_api.tokenized_assets.tokenized_assets_order_submit(signed_order={
        "key": "<value>",
    }, signature="<value>", extension="m2a", quote_id="<id>")

    # Handle response
    print(res)
{
  "order_hash": "0x14459af3a06abf6f7a0d3c2c1fa3b64d2e1b8a7c5e3d2b1f0a9876543210596b",
  "submitted_at": "2026-05-04T11:42:31Z"
}

Documentation Index

Fetch the complete documentation index at: https://docs.compasslabs.ai/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

x-api-key
string
header
required

Your Compass API Key. Get your key here.

Body

application/json

Relay an owner-signed Fusion order to the 1inch relayer.

The shape mirrors what POST /order returned plus the wallet's EIP-712 signature — all fields are required by the upstream relayer. Maker is the Tokenized Assets Account (the Safe), so the signature is validated via ERC-1271 (Safe.isValidSignature) at fill time rather than as an EOA personal-sign.

signed_order
Signed Order · object
required

The Fusion order struct returned by /order (order.order_message). maker is the Tokenized Assets Account, not the EOA owner — relay this dict back to the API verbatim.

signature
string
required

EIP-712 signature produced by wallet.signTypedData(order.safe_message_eip712) from the /order response. The Tokenized Assets Account validates this via ERC-1271 (Safe.isValidSignature) at fill time, so the signature must be the owner's signature over the SafeMessage hash, not the raw Fusion order hash. For a single-owner Safe this is the standard 65-byte ECDSA (r, s, v) blob; multi-owner Safes and pre-approved-hash flows produce variable-length signatures and are also accepted — the relayer enforces its own checks downstream.

extension
string
required

Opaque hex blob from the /order response — pass back unchanged.

quote_id
string
required

order.quote_id from the /order response.

order_hash
string | null

EIP-712 order hash from order.order_hash in the /order response. Optional but recommended: 1inch's relayer occasionally accepts a submit with a 2xx empty body; passing the hash through lets the API still return a usable handle for status / cancel lookups instead of failing.

Response

Successful Response

Returned after the signed order is relayed to 1inch Fusion.

order_hash
string
required

On-chain order hash for status / cancel lookups.

submitted_at
string
required

Server-side ISO 8601 UTC timestamp at which the order was relayed.