## 📄 Standard API Reference Template

Use this exact structure (with consistent heading hierarchy and table formats) for all API endpoint or operation reference documentation. Adapt only by adding or omitting sections that are genuinely not applicable.

```markdown
## [METHOD] /path/to/resource/{id}

One-sentence description of the operation's purpose.

### Overview

2-4 sentences explaining what the operation does, when it is typically used, and any important conceptual context.

### Authentication

Describe the required authentication mechanism and how credentials are passed.

### Path Parameters

| Name | Type | Required | Description |
|------|------|----------|-------------|
| id   | uuid | Yes      | Unique identifier of the resource. |

### Query Parameters

[Table or "None"]

### Headers

[Table]

### Request Body

[Schema description + example JSON]

### Responses

#### 200 OK

[Description + example]

#### 4xx Errors

| Status | Code | Description | How to Resolve |
|--------|------|-------------|----------------|

### Examples

#### cURL

```bash
curl command here
```

#### TypeScript (SDK)

```typescript
code example
```

### Related Resources

- Links to tutorials that demonstrate this operation
- Links to related reference pages
- Links to relevant webhooks or events
```

Maintain this template's consistency across the entire reference section to create a predictable, scannable experience for readers.