Overview
Order types determine how an order is executed in the market. Different order types provide different trade-offs between execution certainty and price control. Before submitting an intent, verify that the target broker supports the requested order type. Requests using unsupported combinations of order type, destination, or time-in-force will be rejected.Intent API support
The current intent request schema accepts four order specifications:
This table describes order types that can be submitted through
POST /v1/intents. Broker event and ledger models may contain additional order types observed from broker-side activity.
Trailing stop is not yet accepted.
TrailingStop is absent from the intent request schema, so an intent naming it is refused rather than routed. This is a platform limit rather than a broker one, and it applies to every broker above.Trailing stops placed directly with a broker are still reported: they appear in broker events and the ledger like any other order. Only submission through the intent API is pending.Order Type Definitions
Examples
Each order specification is nested belowcommand.payload.spec. Numeric quantities and prices are strings.
Notes
- Valid order-type, route, and time-in-force combinations remain broker-dependent.
- Additional exchange, routing, environment, and account restrictions may apply.
- A request can be accepted as an intent and later rejected by the broker. Monitor intent actions and order events for the final outcome.