Omni AI
ModelsExpand Collapse
ContentPartStructuredActionPayload { action, action_id }
Structured action content part.
Structured actions that Omni AI can return to clients.
These actions provide machine-readable instructions for the client to execute, such as prefilling an order ticket, opening a chart, or navigating to a route.
PrefillOrder { prefill_order }
OpenEntitlementConsent { open_entitlement_consent }
Open entitlement consent flow
open_entitlement_consent: OpenEntitlementConsentAction { agreement_key, reason, requested_entitlement_codes, trading_account_ids }
PrefillNewOrderAction { orders }
New-order prefill action.
Orders to prefill using the same shape accepted by the orders API.
quantity: string
Quantity to trade. For COMMON_STOCK: shares (may be fractional if supported). For OPTION (single-leg): contracts (must be an integer)
id?: string | null
Optional client-provided unique ID (idempotency). Required to be unique per account.
expires_at?: string | null
The timestamp when the order should expire (UTC). Required when time_in_force is GOOD_TILL_DATE.
extended_hours?: boolean | null
Allow trading outside regular trading hours. Some brokers disallow options outside RTH.
symbol?: string | null
Trading symbol. For equities, use the ticker symbol (e.g., “AAPL”).
For options, use the OSI symbol (e.g., “AAPL 250117C00190000”).
Either symbol or instrument_id must be provided.
PrefillOrderAction = PrefillNewOrderAction { action_type } | PrefillCancelOrderAction { action_type }
Action to prefill order details for user confirmation.
The user must review and authorize the order before submission to the trading API. This action provides parsed order data that can be used to prefill an order ticket UI or submitted directly via the orders API after user confirmation.
StructuredAction = PrefillOrder { prefill_order } | OpenChart { open_chart } | OpenScreener { open_screener } | OpenEntitlementConsent { open_entitlement_consent }
Structured actions that Omni AI can return to clients.
These actions provide machine-readable instructions for the client to execute, such as prefilling an order ticket, opening a chart, or navigating to a route.
PrefillOrder { prefill_order }
OpenEntitlementConsent { open_entitlement_consent }
Open entitlement consent flow
open_entitlement_consent: OpenEntitlementConsentAction { agreement_key, reason, requested_entitlement_codes, trading_account_ids }
Omni AIEntitlements
Thread-centric AI assistant for conversational trading. Create threads to start conversations, poll response objects for in-progress output, and read finalized messages from thread history. Thread/message/response endpoints require an explicit account_id. Entitlement endpoints are caller-scoped and use trading_account_ids.
Get Entitlements
Create Entitlements
Delete Entitlement
Get Entitlement Agreements
ModelsExpand Collapse
EntitlementAgreementResourceList = Array<EntitlementAgreementResource { agreement_id, agreement_key, document_content, 4 more } >
EntitlementResourceList = Array<EntitlementResource { agreement_id, entitlement_code, entitlement_id, 2 more } >
Omni AIMessages
Thread-centric AI assistant for conversational trading. Create threads to start conversations, poll response objects for in-progress output, and read finalized messages from thread history. Thread/message/response endpoints require an explicit account_id. Entitlement endpoints are caller-scoped and use trading_account_ids.
Get Message By ID
Submit Feedback
Omni AIResponses
Thread-centric AI assistant for conversational trading. Create threads to start conversations, poll response objects for in-progress output, and read finalized messages from thread history. Thread/message/response endpoints require an explicit account_id. Entitlement endpoints are caller-scoped and use trading_account_ids.
Get Response By ID
Cancel Response
ModelsExpand Collapse
Omni AIThreads
Thread-centric AI assistant for conversational trading. Create threads to start conversations, poll response objects for in-progress output, and read finalized messages from thread history. Thread/message/response endpoints require an explicit account_id. Entitlement endpoints are caller-scoped and use trading_account_ids.