JIT report types and file responses on the JIT reports endpoint

Broker API

The JIT reports reference now matches what the API actually serves. No API behavior changes.

report_type documents every supported report: detail_v2, gross_summary_v2, net_summary_v2, obligation_v2, settlement and balance, plus the legacy aliases summary (for gross_summary) and payment (for gross_payment). Each value now carries a short description. Which reports you receive depends on your JIT configuration, and the _v2 suffix names a file format, not a JIT generation.
With response_type=inline or omitted, the endpoint returns the report file itself: text/csv for CSV reports and application/pdf for payment reports, with a Content-Disposition header naming the file. The spec previously declared a JSON body for this case.
With response_type=download_url, the endpoint returns JSON with a temporary url, filename and expires_at, as before. The example filename now matches the real format, for example ALPC-2026-04-14-common_stock-detail.csv.
Generated SDKs only handle the JSON response: set response_type=download_url and download the file from url.
The JITReport schema, which described report files as JSON fields, has been removed; no response ever had that shape.
system_date now has an example.