Skip to main content

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.

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.

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 https://api.writerzroom.com/api/templates
Authorization: Bearer YOUR_API_KEY
{
  "templates": [
    {
      "id": "blog_article_generator",
      "name": "Blog Article",
      "category": "marketing",
      "description": "Long-form educational, informative, or thought leadership content"
    },
    {
      "id": "research_paper_template",
      "name": "Research Paper",
      "category": "academic",
      "description": "Formal, evidence-driven, analytically structured content"
    }
  ]
}

Get Template by Slug

GET https://api.writerzroom.com/api/templates/{slug}
Authorization: Bearer YOUR_API_KEY

Supported Operations

OperationDescription
List templatesRetrieve all available templates
Get templateRetrieve one template by slug
Read metadataAccess name, type, description, category, and required input fields
Build formsUse template fields to generate frontend input forms

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.
Avoid hardcoding template catalogs in production integrations. Fetch templates from the API so your interface stays aligned with WriterzRoom updates.
A template controls content type, required inputs, structure, section expectations, and output format.
Templates define the structure of the output. Style profiles define tone, voice, pacing, audience fit, and writing behavior.
Use /templates/{slug} before generation when you need to build dynamic forms or validate required fields.

Style Profiles API

Retrieve available writing styles for generation setup.

Generate Content

Submit a request using the selected template.
Last modified on May 17, 2026