Summary: Instrument responses now include trading data

Instruments

New Fields

The InstrumentResponse schema now exposes trading data, so partners can determine how, when, and by whom an instrument can be traded. This affects the following endpoints:

• GET /instruments - List instruments
• GET /instruments/{isin} - Get an instrument

New fields:

• complexity - MiFID II complexity classification (non_complex / complex).
• knowledge_and_experience_profile - the minimum K&E profile required to purchase the instrument (basic / extended).
• product_category - the product category whose keys match the customer experience data returned by GET /accounts/{account_id}/experience.
• days_to_settle - business days from trade date to settlement (T+n).
• trading - a list of supported order type / venue combinations, each with minimum_quantity and, for batch orders, batch_cutoff and (when required) prefunding_cutoff. An empty list means orders are currently not supported.

Note: These fields are being rolled out gradually and are activated per partner. Until enabled for your account, they are absent from the response. New Sandbox test ISINs are documented on GET /instruments/{isin} for trying the different trading configurations.