Templates API - WriterzRoom

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.

Generation

Guides request setup before submission.

List Templates

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

{
  "success": true,
  "data": {
    "items": [
    {
      "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"
    }
    ],
    "count": 50,
    "page": 1,
    "limit": 100
  }
}

Get Template by Slug

GET https://api.writerzroom.com/api/templates/{slug}?vertical_id=healthcare
Authorization: Bearer YOUR_API_KEY

The response includes a length block: the template’s word bounds, deliverable_max (the longest range any tier can finish in its time budget), tiers (per tier, the longest range it can finish, max_words, and why it is ruled out regardless of length, excluded), its substantive floor, the default preset, and each preset with its range and, per tier, whether that tier can deliver it and why not. Pass vertical_id to include the context’s rules; a context whose verification blocks unverified content rules out Quick. length is null for page-sized templates such as feature screenplays.

"length": {
  "bounds": {"min": 1200, "max": 4200},
  "floor": 1200,
  "default": "standard",
  "presets": [
    {"id": "brief", "label": "Brief", "min": 1200, "max": 2200,
     "tiers": {"quick": {"available": true, "reason": null, "estimated_seconds": 134}, "...": {}}}
  ]
}

The response also includes parameter_constraints. It is null for most templates. For a template that declares which of its options can be combined, it lists each rule: the options it applies when chosen, the values it excludes, the bounds it requires, and the reason shown when a request breaks it, plus the options resolved from auto at submission. Generation refuses a request that breaks a rule with a 422 before anything is charged; see Generate content.

"parameter_constraints": {
  "rules": [
    {"id": "bootcamp_duration", "when": {"course_format": ["bootcamp_intensive"]},
     "exclude": {"course_duration": ["12_weeks_semester", "16_weeks_semester"]}, "require": {},
     "reason": "A bootcamp is an intensive, fixed-length program; choose 1, 4 or 8 weeks, or a semester-style format."}
  ],
  "resolve_auto": ["total_learning_hours"]
}

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

Fetch available templates

Call GET /templates to retrieve the current template catalog.

Select a template

Use the template slug as the template_id in generation requests.

Read input requirements

Retrieve template details to understand required fields and optional parameters.

Build the request form

Use the template response to guide user input collection.

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?

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?

A template controls content type, required inputs, structure, section expectations, and output format.

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.

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.

​Template Overview

Structure

Inputs

Category

Generation

​List Templates

​Get Template by Slug

​Supported Operations

​Integration Flow

​Best Practice

Style Profiles API

Generate Content

Template Overview

List Templates

Get Template by Slug

Supported Operations

Integration Flow

Best Practice