Journal responses corrected with distinct JNLC and JNLS schemas

Broker API

Journal responses are now described as complete JNLC (cash) and JNLS (securities) schemas composed from a shared journal base and selected by an explicit entry_type discriminator, so generated clients preserve the actual wire response.

• The Journal schema is now a discriminated union of JNLC and JNLS rather than a partial composition, with each variant carrying all shared journal fields.
• Batch journal responses are modeled as BatchJournalResponseJNLC and BatchJournalResponseJNLS, with an optional error_message on a failed item and refreshed examples.
• The batch and reverse batch descriptions now match behavior: a successful reverse batch returns an array of JNLC journals, and if any account or entry is invalid the whole batch is canceled with no per-item error result.
• Required and nullable journal fields (symbol, qty, price, settle_date, system_date, net_amount) are corrected so null values round-trip.
• legs on the OrderLeg schema is documented as always null, with an empty array also accepted for generated-client compatibility.

Affected Endpoints

• POST /v1/journals
• GET /v1/journals
• GET /v1/journals/{journal_id}
• POST /v1/journals/batch
• POST /v1/journals/reverse_batch
• POST /v1/trading/accounts/{account_id}/orders
• GET /v1/trading/accounts/{account_id}/orders
• GET /v1/trading/accounts/{account_id}/orders/{order_id}
• PATCH /v1/trading/accounts/{account_id}/orders/{order_id}
• GET /v1/trading/accounts/{account_id}/orders:by_client_order_id

Trading API

legs on the OrderLeg schema now also accepts an empty array in addition to null, for generated-client compatibility. Order legs are still never nested beyond one level, and the returned values are unchanged.

Affected Endpoints

• GET /v2/orders
• GET /v2/orders/{order_id}
• GET /v2/orders:by_client_order_id
• POST /v2/orders
• PATCH /v2/orders/{order_id}
• DELETE /v2/positions
• DELETE /v2/positions/{symbol_or_asset_id}