Use the Templates API to discover available templates programmatically and retrieve template details before starting a generation flow. This is useful when building a custom front end, internal selection layer, or automated content workflow.Documentation Index
Fetch the complete documentation index at: https://docs.writerzroom.com/llms.txt
Use this file to discover all available pages before exploring further.
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
| Operation | Description |
|---|---|
| List templates | Retrieve all available templates |
| Get template | Retrieve one template by slug |
| Read metadata | Access name, type, description, category, and required input fields |
| Build forms | Use template fields to generate frontend input forms |
Integration Flow
Read input requirements
Retrieve template details to understand required fields and optional parameters.
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.