Template Overview
Structure
Defines the content format and sections.
Inputs
Defines required user-provided fields.
Category
Groups templates by content purpose.
Generation
Guides request setup before submission.
List Templates
Get Template by Slug
Supported Operations
Integration Flow
1
Fetch available templates
Call
GET /templates to retrieve the current template catalog.2
Select a template
Use the template slug as the
template_id in generation requests.3
Read input requirements
Retrieve template details to understand required fields and optional parameters.
4
Build the request form
Use the template response to guide user input collection.
5
Submit generation
Send the selected template, style profile, and structured input to
POST /api/generate.Best Practice
Use template detail responses to drive your form layer. This makes your integration more resilient because input requirements come from the template definition instead of hard-coded assumptions.Should templates be hardcoded?
Should templates be hardcoded?
Avoid hardcoding template catalogs in production integrations. Fetch templates from the API so your interface stays aligned with WriterzRoom updates.
What does a template control?
What does a template control?
A template controls content type, required inputs, structure, section expectations, and output format.
How does this relate to style profiles?
How does this relate to style profiles?
Templates define the structure of the output. Style profiles define tone, voice, pacing, audience fit, and writing behavior.
Style Profiles API
Retrieve available writing styles for generation setup.
Generate Content
Submit a request using the selected template.