Export an analysis (ideas-json)
Structured JSON export (schemaVersion 2) for one COMPLETED, export-ready analysis. Deep runs include full sections, pivots, citations, and generated module payloads.
Authorizations
Your API key (prv_...), sent as-is. It is the only credential the API needs - see the Authentication guide.
Path Parameters
Run id (returned by create) or report id.
Query Parameters
ideas-json Response size. "full" is the whole payload. "summary" drops section prose and the Google Trends data points - together about two thirds of a deep report - and keeps every scored field: score, verdict (including the Bottom Line narrative under details.verdict.narrative), competitors, market size, risks, pivots, citations, plus the closing verdict under details.sections.synthesis. What it left out is listed under idea.details.omitted. This operation defaults to "full"; the batch export takes the same parameter but is meant to be called with "summary".
full, summary Response
The export payload.
ideas-json export, schemaVersion 2. Deep-only fields are null on free runs. See the Scans and Enrichment guide for the field-by-field contract.
analysis The verbosity this payload was built at, echoed back. On "summary", idea.details.omitted names what was dropped.
full, summary 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.
Purchase context for a locked export or buyable quota refusal. Export upsells are free-owner only; a paid non-regional caller may receive a scan_pack top-up on INSUFFICIENT_TOKENS. Ignore it if you only need the data contract.