Template lifecycle

Template versions and environments

Promote immutable template versions through development, staging, and production.

Reviewed 2026-08-05 · PDFDesignAPI Engineering

Immutable versions

Every template save creates a numeric version. A numeric version is stable and can be selected for deterministic rendering.

Environment aliases

Development advances with editor saves. Staging and production change only through explicit promotion.

Use staging for integration and visual regression tests, then promote the verified version to production.

Inspect the selected contract

GET /api/v1/templates/:templateUuid/version/:version returns a selected version contract.

GET /api/v1/templates/:templateUuid/environment/:environment resolves a named environment and its contract.

Rollback

If a newly promoted layout causes a regression, point the environment back to the last verified immutable version and investigate outside the production path.

Was this page helpful?

Need help with an implementation detail?

Contact technical support →