The WriterzRoom API exposes generation, status tracking, content management, templates, style profiles, verticals, and dashboard usage endpoints through one versioned base URL.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.
Endpoint Overview
Generation
Submit jobs and poll completion status.
Content
Retrieve, save, and manage generated drafts.
Configuration
Fetch templates, styles, and vertical settings.
Usage
Review account statistics and activity.
Base URL
Core Endpoints
| Method | Endpoint | Description |
|---|---|---|
POST | /generate | Submit a generation request |
GET | /generate/status/{request_id} | Poll generation status and retrieve completed content |
GET | /content | List saved content for the authenticated user |
GET | /content/{contentID} | Retrieve a specific content item |
POST | /content/save | Save or update a content item |
POST | /content/regenerate-section | Regenerate a specific section of existing content |
GET | /templates | List available templates |
GET | /templates/{slug} | Retrieve a specific template by slug |
GET | /style-profiles | List available style profiles |
GET | /style-profiles/{slug} | Retrieve a specific style profile by slug |
GET | /verticals | List available verticals |
GET | /verticals/{vertical_id} | Retrieve vertical configuration details |
GET | /dashboard/stats | Retrieve usage statistics and generation counts |
Request Example
Error Response Example
Integration Flow
Fetch valid configuration
Use
/templates, /style-profiles, and /verticals to retrieve valid identifiers before submitting generation jobs.Submit generation
Call
POST /generate with the selected template, style profile, vertical, generation mode, and structured input.Poll for completion
Use
/generate/status/{request_id} to retrieve processing updates and completed content.Rate Limits
| Limit | Value |
|---|---|
| Per-account request rate | 10 requests per minute |
| Rate limit response | 429 |
| Recommended retry strategy | Exponential backoff |
| Generation accounting | Monthly plan usage |
Error Codes
| Status | Meaning |
|---|---|
400 | Bad request, missing fields, or invalid payload |
401 | Unauthorized, missing or invalid API key |
403 | Forbidden, plan does not include API access |
404 | Resource not found |
429 | Rate limit exceeded |
500 | Internal server error |
Exponential Backoff Example
Operational Guidance
Which base URL should integrations use?
Which base URL should integrations use?
Use
https://api.writerzroom.com/v1 for public API integrations.Should identifiers be hardcoded?
Should identifiers be hardcoded?
Avoid hardcoding identifiers for large integrations. Fetch templates, style profiles, and verticals programmatically when possible.
How should rate limits be handled?
How should rate limits be handled?
Treat
429 as a retryable response and apply exponential backoff. Do not retry immediately in tight loops.What information should be included in support requests?
What information should be included in support requests?
Include the endpoint, timestamp, request ID if available, response status, and sanitized error body.
API Authentication
Learn how to authenticate API requests.
Check Generation Status
Poll submitted generation jobs until completion.