Get render sources for a page

Returns references only (path + identifier, no file content, no container code) mapping a rendered page to its source files. The page is identified by a URI path segment, exactly like GET /api/v1/page/render/{uri}.

The URI must be a plain path (e.g. index, about/team). To address a specific site, use the host_id query parameter.

Includes the page reference, theme VTL files, all containers referenced by the template (only content types actually placed under the applied persona/variant are included), and widget contentlets placed on the page.

Widget source field: Each widget entry includes a source field:

• FILE — the widget's Velocity lives in a file asset; path and identifier are populated. Retrieve the VTL content via GET /api/v2/assets.
• CODE — the widget's Velocity is inline (in the content type's widgetCode field and/or the contentlet's own fields). No path/identifier are returned. Retrieve the content type definition via GET /api/v1/contenttype/id/{contentTypeVar} and the placed contentlet via GET /api/v1/content/id/{contentletId}.

Other source lookups:

• Theme folder files: GET /api/v1/folder/sitename/{site}/uri/{uri}
• DB container code: GET /api/v1/containers/working?containerId=<id>&includeContentType=true
• FILE container VTL content: GET /api/v2/assets