Documentation

Galley Render turns a template plus a JSON payload into a PDF, PNG or JPG behind a signed URL. Every render is deterministic and cached, so the same input always returns the same file and an identical repeat call costs nothing.

If you have never rendered anything here, start with the quickstart — it goes from nothing to a signed PDF without an account.

Start here

Page	What it covers
Quickstart	Keyless trial to first render, then the same call with a key
Authentication	glr_sk_… keys, both accepted headers, and key hygiene
Template gallery	The 22 starter templates, with schemas and example payloads
Free tools	Render something in the browser before you write any code

The API

POST /v1/render is the one endpoint most integrations need.

Page	Endpoint
Render	POST /v1/render
Batch render	POST /v1/render/batch
Get a render	GET /v1/renders/:id, GET /v1/renders
Templates	GET /v1/templates, GET /v1/templates/:ref
Create a template	POST /v1/templates
Template versions	POST /v1/templates/:name/versions
Validate a payload	POST /v1/templates/:ref/validate
Usage	GET /v1/usage
OpenAPI	The machine-readable description

Templates

A template is one self-contained HTML document with inline CSS and Liquid expressions, plus a JSON Schema for its payload. Versions are immutable.

• Template language
• Engines — Chromium for anything PDF, Satori for fast PNG cards
• Versions
• Data schemas

Running it in production

• Caching and signed URLs — how the cache key is built, and why a hit is free
• Webhooks
• Errors — every type, its status, and what to do about it
• Spend caps and limits
• Assets, fonts and images
• Security
• SDKs and clients

For agents

• The MCP server — ten tools, no key needed to begin
• Claude Code · Cursor · OpenAI Agents SDK
• Skill file and llms.txt

Guides

Eight worked how-tos, each with code you can run: all guides.