Templates
Publish a new immutable version
Earlier versions keep rendering byte-for-byte as they did. Renders cached against the old version stay valid; the new version starts with a cold cache.
Fields you leave out are inherited from the previous version, not reset. engine, schema, options, expected_pages and example all carry forward, so {"source": "…"} publishes a new body against the same renderer and the same validation contract. Send a field to override it, and send an empty value ({} for schema or options, null for example) to clear it. source is always required, and message is never inherited — it is the note for this version.
post/v1/templates/{name}/versions
Request
- Base URL: https://api.galleyrender.com
- URL: https://api.galleyrender.com/v1/templates/{name}/versions
- Auth: HTTP bearer
Path parameters
namestring required
Example:invoice
The template name, without a version.
Request body
Example request
{
"name": "invoice",
"options": {
"margin": "18mm"
}
}Response
Published.
Example response
{
"id": "tpl_5m2k8q1xv7bd",
"ref": "invoice@1"
}Changes
No recorded changes to this operation across all 1 revision of this API.