1.5 KiB
1.5 KiB
{Module Name} — API Workspace Module
Use this template when adding or editing API endpoint documentation modules.
Module Metadata
Every module MUST start with:
<!-- module: <short_name> -->
<!-- description: One-line description of what this module covers -->
<!-- depends: <comma-separated list of dependency module names> -->
Endpoint Template
Each endpoint MUST use this structure:
METHOD /path/to/endpoint
Auth: Required / Optional / Public
Scope: file-level / identity-level / system-level
Request Parameters
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
param1 |
string | Yes | — | Description |
Example
# brief description of what this example demonstrates
curl -s -X METHOD "$API/path" \
-H "X-API-Key: $KEY" \
-H "Content-Type: application/json" \
-d '{"param1": "value"}'
Response (200)
{ "success": true }
| Field | Type | Description |
|---|---|---|
success |
boolean | Always true on 200 |
Error Codes
| Code | HTTP | When |
|---|---|---|
| E0xx | 4xx | Description |
Rules
- Each module file covers ONE topic group (e.g.,
09_tmdb.md= all TMDb endpoints) - Use
$APIand$KEYin all curl examples - Use
$FILE_UUID,$IDENTITY_UUIDvariables for UUID examples - Module filename =
NN_topic.md(NN = execution order, 01-99) dependsmetadata = which modules must be assembled before this one