Project
A project owns templates, uploaded assets, API keys, a plan, and a generation count. The dashboard calls it a project, and the API reference calls it a workspace. Every account has a Personal project, and you can create team projects. Manage projects and members explains how.Template
A template is a design on a canvas. You build it in the template editor or start from a template in the gallery. A template renders to a PNG, JPEG, or WebP image, or to a PDF.Template id
The template id tells the API which template to render. It looks liketpl_xxx. Open the menu on a template card and click Copy Template ID.
Canvas
The canvas is the drawing area of a template. Its width and height are the size of the image or PDF page, in pixels. A request cannot change the canvas size.Layer
A layer is one element on the canvas, such as text, an image, a QR code, a barcode, or a table. Give a layer a name when you want to change it from the API. Elements lists the layer types.Modification
A modification sets new values for one layer. It has aname that picks the layer, and fields such as text, src, or color that change it. A request carries a list of modifications, and a layer that you leave out keeps the value from the template. Modifications lists every field.
Generation
A generation is one render of a template into a file. Each successful render counts toward your quota, with a few exceptions that Quota and limits lists. To review past renders, open Generations in the sidebar, or open the menu on a template card and click View generations. Each row shows the time, the template, the format, the size, and whether the render was billed, and you can copy the modifications that the request sent. See your generations has more.Direct, stored, and signed
You can get a generated file in three ways.
Generate images, Generate PDFs, and Signed URLs show each one.