Reference
Public Content API
Read-only API for published posts, journal entries, and pages. Use explicit endpoints:
.json for JSON and .md for markdown.
Posts
Access published blog posts as structured JSON or raw markdown.
Returns all published posts sorted by publication date descending.
Parameters
This endpoint does not accept parameters.
Returns
A list object with compact post metadata (no full content body).
Returns one post including full markdown content.
Parameters
-
slugstring required - The post slug (for example: the-startup-minded-engineers).
Returns
A post object with metadata and full markdown body.
Returns the raw markdown document including frontmatter.
Parameters
-
slugstring required - The post slug.
Returns
A text/markdown response with frontmatter + markdown body.
Journal
Access weekly journal entries in JSON or markdown format.
Returns all published journal entries sorted by publication date descending.
Parameters
This endpoint does not accept parameters.
Returns
A list object with journal metadata.
Returns one journal entry with full markdown content.
Parameters
-
slugstring required - The journal slug (for example: 2025-11-16).
Returns
A journal_entry object with metadata and full content.
Returns journal entry markdown including frontmatter.
Parameters
-
slugstring required - The journal slug.
Returns
A text/markdown response with frontmatter + markdown body.
Pages
Access static pages such as About in JSON or markdown format.
Returns all public static pages.
Parameters
This endpoint does not accept parameters.
Returns
A list object with page metadata.
Returns one static page with full markdown content.
Parameters
-
slugstring required - The page slug (for example: about).
Returns
A page object with metadata and full content.
Returns raw page markdown including frontmatter.
Parameters
-
slugstring required - The page slug.
Returns
A text/markdown response with frontmatter + markdown body.
Errors
This API is deployed as static files. Unknown API paths return the site's HTML 404 page.
Current deployment (Cloudflare Pages static)
- Known prebuilt endpoints return
200. -
Unknown paths (for example
/api/posts/invalid-slug.json) return the platform/site HTML404page.
Optional runtime mode
If you move these routes to runtime Functions/SSR later, you can return a consistent JSON error object with:
not_found: resource is missing (404)invalid_request: malformed input (400)internal_error: unexpected server error (500)