Skip to main content
Generate preview renderings of creative manifests. Supports both single creative preview and batch preview (5-10x faster for multiple creatives). Request Schema: /schemas/3.0.19/creative/preview-creative-request.json Response Schema: /schemas/3.0.19/creative/preview-creative-response.json

Quick Start

Single Creative Preview

Response:
Embed the primary render in an iframe:

Direct HTML Embedding

For faster rendering without iframe overhead, request HTML directly:
Response contains raw HTML:
Only use output_format: "html" with trusted creative agents. Direct HTML embedding bypasses iframe sandboxing.

Batch Preview (Multiple Creatives)

Preview multiple creatives in one API call (5-10x faster):
Response contains results in order:

Variant Preview (Post-Flight)

Preview what a specific variant looked like when served. Use variant_id from get_creative_delivery response:
Response:
Since each variant from get_creative_delivery includes its full manifest, you can also pass the manifest directly to preview_creative as a standard single request to re-render it.

Request Parameters

All modes use a single flat object with request_type as the discriminant. Required column values: Single = required when request_type is "single", Batch = required when "batch", Variant = required when "variant".

Input Sets

Generate multiple preview variants by providing different contexts:
Available macros: DEVICE_TYPE, COUNTRY, CITY, DMA, GDPR, US_PRIVACY, CONTENT_GENRE, etc. Context descriptions: For AI-generated content like host-read audio ads.

Response Format

Single Mode Response

Batch Mode Response

Preview Structure

Multi-render formats: Some formats produce multiple pieces (video + companion banner). Each has its own render_id and role.

Previewing generative creative

For generative formats — contextual display, AI-generated native, conversational ads — the creative doesn’t exist until serve time. Preview serves two distinct purposes:

Pre-flight: representative samples

Before the campaign runs, use single or batch mode to preview what the agent could generate given different contexts. Pass inputs with context_description to simulate serve-time conditions:
These previews are representative, not definitive. Real serve-time output depends on live signals (actual page content, user device, time of day) that can’t be fully simulated. Use draft quality for fast iteration on the brief and creative direction, then production quality for stakeholder review.

Post-flight: exact replay

After the campaign runs, use variant mode to see exactly what was served. Pass a variant_id from get_creative_delivery:
The response includes the variant’s actual manifest — the specific headline, image, and layout the agent generated for that context. This is a faithful replay, not a re-generation.

Setting expectations

For generative formats where every impression produces a different creative (like AI chat or real-time contextual), pre-flight previews are best understood as samples from a distribution rather than the ad. The brief and brand identity constrain the distribution; previews let you verify the agent interprets those constraints correctly.

Conversational and interactive formats

For formats where the ad is stateful — AI chat, interactive experiences, conversational native — preview takes on additional meaning:
  • Pre-flight renders a representative first interaction or simulated conversation. The interactive_url field in the preview response (when present) provides a sandbox where reviewers can interact with the experience directly. Use context_description to simulate different conversation entry points.
  • Post-flight variant replay shows the actual exchange that occurred. For multi-turn formats, the variant manifest captures the full content the agent produced (message sequence, responses, media assets shown). The level of detail depends on the agent — some provide full transcripts, others provide summarized content with anonymized user signals.
These formats have the widest gap between pre-flight and post-flight: a pre-flight preview can only approximate one possible conversation path, while the live experience adapts to each user. Preview enough scenarios to verify tone, guardrails, and brand consistency.

Quality mismatch

If the requested quality level is not supported, the agent renders at the best quality it can provide. The protocol does not require agents to support both levels — an agent that only generates at one fidelity ignores the parameter. There is no response field echoing back the actual quality used, so if quality accuracy matters for your workflow, verify by visual inspection or ask the agent about its capabilities through list_creative_formats.

Preview expiration and variant retention

All previews have an expires_at timestamp. After expiration, preview URLs return errors and must be re-generated. For generative creative, re-generating a pre-flight preview may produce different output — the same brief and context can yield different creative each time. Variant previews (post-flight) depend on the agent retaining variant data. Agents are not required to retain variant data indefinitely. If you request a variant preview for a variant the agent has purged, expect a standard error response. For long-running campaigns, retrieve and archive variant previews periodically rather than assuming they will remain available.

Examples

Device Variants

Batch with HTML Output

Preview multiple creatives for a grid layout:

AI-Generated Audio Preview

HTTP Status Codes

Single mode:
  • 200 OK - Preview generated successfully
  • 400 Bad Request - Invalid manifest or format_id
  • 404 Not Found - Format not supported
Batch mode:
  • 200 OK - Batch processed (check individual success fields)
  • 400 Bad Request - Invalid batch structure

Key Points

  • Every render’s preview_url returns an HTML page for iframe embedding
  • Use output_format: "html" for grids of 10+ previews (no iframe overhead)
  • Batch mode is 5-10x faster than individual requests
  • Preview URLs expire (check expires_at)
  • Handle partial batch failures by checking each result’s success field