Export a batch (ideas-json)
Structured export for a batch. Includes only completed, export-ready items; every skipped item is listed in omittedItems with a reason. A single exportedAt is pinned per export so the same batch state always serializes identically.
Authorizations
Query Parameters
Response size, applied to every idea in the batch. Same two values and the same wire default as the single-analysis export ("full" when the parameter is omitted), but send "summary" here: a batch multiplies one report by up to five, and a full batch of deep reports will not fit a tool-result limit. "summary" drops section prose (keeping the closing verdict under details.sections.synthesis) and Trends data points, shortens other text on the largest reports without touching scores or ratings, and lists what it changed under details.omitted on each idea.
full, summary Response
The batch export payload.
Note the asymmetry with the other two exports: this one carries no exportType. The single-analysis and agency-report exports each stamp one, this payload identifies itself by batchId instead, and the schema follows the wire rather than inventing a discriminator that is never sent.
Which fields this export left null, and why. Present only when the caller's tier withheld something, and absent entirely when the payload is complete. Read it before concluding a field is absent: a null under one of these paths is locked, not missing and not a failed analysis. It ships to every tier, paid included, and carries no price and no URL. On a batch export there is ONE object for the whole batch, the union of every exported item's withheld fields, deduplicated by path.