Deploy a market for an asset
Triggers on-chain deployment of a compliance-gated secondary market for a deployed asset. If the asset is not yet deployed on the target chain, the system will auto-bridge the asset first, then automatically deploy the market once the bridge completes — no extra user interaction needed. The deployment is processed asynchronously via CQRS — returns 202 Accepted immediately. Fee collection is configured with the org wallet as fee collector and Signum protocol wallet for protocol fees. Poll the market detail endpoint for deployment status updates.
Authentication
JWT access token from POST /auth/login or POST /oauth/token
Organization-scoped API key created via POST /orgs/:orgId/api-keys. Carries permission grants.
Path parameters
Request
LayerZero endpoint ID of the target chain (defaults to HyperEVM 40362)
Address of the deployed RWA token on the target chain. If omitted and asset is not yet deployed on the target chain, the system will auto-bridge first.
Regulation framework (reg_d | reg_s | reg_a_plus | reg_cf | none)
Blocked country codes (ISO 3166-1 alpha-3)
Unix timestamp when lockup period ends (0 = no lockup)
Maximum number of holders (0 = unlimited)
Max tokens per holder as string for precision (0 = unlimited)
Taker fee in basis points (default: 30)
Maker fee in basis points (default: 0)