Preview Every Layout Before You Personalize with CHILI GraFx Environment API
When a design system holds a dozen layout variants – social ads, print formats, animated banners – showing end users a single thumbnail and asking them to guess the rest is a poor experience. It slows decisions, increases errors, and puts unnecessary friction between a user and the output they actually need.
The CHILI GraFx Environment API now removes that friction entirely.
Per-Layout and Per-Page Preview Thumbnails
A GraFx Studio design can contain multiple layouts – variants of the same design at different sizes or for different channels – and each layout can have multiple pages. Until now, the template preview endpoint always returned the preview of the default layout and default page only.
That limitation is gone. You can now request a preview for any specific layout and page combination within a multi-layout design. This unlocks per-layout and per-page thumbnail generation for downstream applications, including GraFx Experience.
What This Means for Integrators and End Users
For integrators and ISVs building portals on top of CHILI GraFx, this opens up a more complete self-serve experience. A design system delivered as a single multi-layout design holds all the variants of a campaign – different sizes, channels, or page sequences – in one place.
Instead of surfacing a single thumbnail, a portal can now render a thumbnail for every variant the design system contains. End users can visually compare each layout and page before choosing the one they want to personalize or export. That is a meaningful step toward truly self-serve content production at scale.
The API Change
Two existing endpoints now accept two new optional query parameters – layoutId and pageId:
GET /api/v1/environment/{environment}/templates/{templateId}/preview
GET /api/v1/environment/{environment}/templates/{templateId}/preview/{previewType}
Key behaviors to know:
- Backwards-compatible: when both parameters are omitted, the endpoint returns the default layout and default page preview exactly as before.
- When either parameter is provided, the preview is rendered – or served from cache – for that specific layout and page combination.
- When either parameter is provided but the rendering engine version is below 2.24.0, the endpoint returns 400 Bad Request with a message indicating the minimum supported engine version.
No breaking changes. Existing integrations continue to work without modification.
For teams building on the CHILI GraFx API-first architecture, this update closes a real gap in the headless production experience. Design systems are built to scale across channels and formats – now the preview layer keeps pace with that ambition.







