Docs-only repo — no code, no build system. README.md is the main guide (auth, pagination, domain model, endpoint index). sections/ has one .md per API resource (~47 files).
Every sections/*.md follows this structure:
- H1 title with
=====underline, H2 per endpoint with-----underline (Setext, not ATX) - Endpoints bullet list with anchor links:
- [Get messages](#get-messages) - Endpoint description as bullet:
* `GET /buckets/1/...`with prose ###### Example JSON Responsethen<!-- START GET /path -->/<!-- END GET /path -->wrapping```jsonblock###### Copy as cURLthen```shellblock using$ACCESS_TOKENand$ACCOUNT_IDenv vars- Write endpoints add
###### Example JSON Requestbefore the cURL **Required parameters**:(bold) with inline or bulleted content, and_Optional parameters_:(italic) typically followed by bullet lists- Reference-style links at bottom:
[1]: https://...,[pagination]: ...
Lives between <!-- START API ENDPOINTS --> and <!-- END API ENDPOINTS -->. New sections go alphabetically.
Imperative verb + description + (#PR): Add API documentation for timeline endpoints (#369)
- No YAML frontmatter
- Don't invent API endpoints — only document real ones
- Don't add files outside
sections/and repo root