HTML/CSS API templates

Generate sales collateral from CRM data and HTML/CSS templates

Build proposal and account layouts once, keep branded assets and settings with the template, and render each variation from named CRM values.

  • HTML and CSS layouts
  • Reusable assets and settings
  • Versioned template IDs
Complex HTML and CSS stored with reusable assets, render settings, and a published template version.
Versioned HTML/CSS template
<main class="report-card">
  <h1>{{title}}</h1>
  <img src="{{chart}}" />
</main>
POST/v1/image/{template_id}
{
  "template_values": {
    "title": "Quarterly results",
    "chart": "https://..."
  }
}
Published version
v12Ready to render
Reusable assets
Interlogo.svgchart.png
Render settings
1200 × 630 · PNG · dark mode

Build your template

Two ways to build, one way to render

Both template types render by ID with named values.

Use cases

Create personalized sales visuals without rebuilding each asset

Explore image templates

Account snapshots

Map prospect, opportunity, or customer data into a reusable visual summary.

Personalized outreach

Generate images with recipient names, company details, relevant metrics, and proof points.

Proposal graphics

Keep pricing, timelines, comparisons, and next steps visually consistent.

Customer updates

Create branded progress and performance summaries from current account data.

HTML/CSS template API

Create the design with HTML and CSS, then render it by ID

Save the layout, assets, and image settings in a versioned template. Each image request sends the template ID and named values.

  1. Build the layout

    Create the template from complex HTML and CSS through the API.

  2. Centralize assets and settings

    Keep fonts, images, dimensions, browser options, and output settings with the design.

  3. Publish and render versions

    Release template changes deliberately while integrations continue rendering by stable ID.

Versioned templates

Keep HTML and CSS out of image requests

Send only the template ID and named values. The saved template provides the layout, assets, settings, and selected version.

  • HTML and CSS

    Build detailed layouts without including the full document in every render request.

  • Saved assets and settings

    Keep fonts, images, viewport details, and output options with the template.

  • Published versions

    Publish an update under the same ID and choose which version to render.

Template API workflow
Template API workflow
Layout
HTML + CSS
Shared
Assets · fonts · settings
Release
Versioned template
Render
Stable ID + named values

HTML/CSS API templates

Build the layout once and render it by ID

Keep complex HTML, CSS, assets, fonts, browser settings, and output options in a versioned template while requests send only the values that change.