Templates
Templates are parameterized, approved endpoint operations. Use a Read, Write, or transaction-capable template when an application or governance feature needs a fixed operation instead of arbitrary query input. They are part of the normal Eve workflow, not an advanced or separate product surface.
Lifecycle
- Create a template with
POST /templates. - List or inspect it with
GET /templatesandGET /templates/{template}. - Update it with
PATCH /templates/{template}or remove it withDELETE /templates/{template}. - Render a template for inspection with
POST /templates/{template}/renderor execute the approved operation withPOST /templates/{template}.
Design Templates For Governance
Keep a template focused on one approved operation. Define its required inputs explicitly, use parameter substitution rather than concatenating caller-controlled values, and give it a description that explains its endpoint effect and data sensitivity.
Use a Read template for retrieval, a Write template for a controlled mutation, and a transaction-capable template only when the endpoint operation requires coordinated execution. Templates can be composed into a workflow or published as an application API, but neither composition grants endpoint access by itself.
Rendering And Safe Review
Use the render route before enabling a new template in a production workflow. Rendering lets an operator inspect the resolved request shape with representative input, then adjust the template, endpoint permissions, and policy before the request can reach the backend.
For sensitive operations, pair templates with least-privilege endpoint RBAC, scoped data grants where applicable, and the relevant masking or policy controls. Template execution stays subject to the caller identity and the endpoint's normal governance checks.