Public API
GET /api/forum/topics returns published forum threads as JSON. No API key is required. Run this request from a terminal or your server:
curl --fail-with-body "https://healthmaxxing.org/api/forum/topics?limit=1"The response is an object with a topics array. Each topic includes id, slug, title, excerpt, body, category, authorName, createdAt, and reply and like counts. The OpenAPI spec describes the complete response.
Build a topic URL as https://healthmaxxing.org/forum/{slug}, using the returned slug. Fetch that URL as HTML or request its Markdown version.
The limit parameter defaults to 90 and is clamped to 1–250; fractional values are truncated. Invalid numeric values use the default. The endpoint has no pagination cursor.
An empty result is {"topics":[]}. HTTP 503 means the listing is temporarily unavailable; retry with a delay. Error responses include error and requestId fields. Requests return an X-Request-Id header for support.
Example response
Illustrative response excerpt; additional topic fields are documented in OpenAPI.
{
"topics": [
{
"id": "example-topic",
"slug": "example-discussion",
"title": "Example discussion",
"excerpt": "A public forum discussion.",
"category": "General",
"authorName": "Example member",
"createdAt": "2026-09-08T00:00:00Z",
"repliesCount": 0,
"likesCount": 0
}
]
}Markdown and agents
Start with /llms.txt to discover public content. Fetch a listed page with Accept: text/markdown, or use its .md URL, to read it as Markdown:
curl --fail-with-body -H "Accept: text/markdown" "https://healthmaxxing.org/developers"Markdown responses use text/markdown; charset=utf-8 and include Vary: Accept. Missing pages return HTTP 404 with recovery links. Page requests that accept neither HTML nor Markdown return HTTP 406.
Healthmaxxing does not publish an MCP server. llms.txt is a content index. Agents can use their own HTTP tools to retrieve the listed resources.
Status check
GET /api/health reports whether the site, backend, and database are answering. It returns HTTP 200 with status "ok", or HTTP 503 with status "degraded" or "down". It never exposes error detail.
curl "https://healthmaxxing.org/api/health"Member-only features
Computer use on Insights, facial analysis, and member dashboards only run for a signed-in member on Healthmaxxing. There is no public way to start them from another app, and no token for automating them.
Members sign in with Google or email. Account sign-in does not provide third-party API credentials, and Healthmaxxing does not act as an OAuth authorization server for other applications.
Predictable URLs
- https://healthmaxxing.org/developers: this Healthmaxxing developer resources page
- https://healthmaxxing.org/openapi.json: OpenAPI 3.1
- https://healthmaxxing.org/.well-known/api-catalog: RFC 9727 API catalog
- https://healthmaxxing.org/llms.txt: agent index and when-to-use guidance
- https://healthmaxxing.org/llms-full.txt: full agent content file
- https://healthmaxxing.org/sitemap.xml: sitemap
- https://healthmaxxing.org/api/health: status check
- https://healthmaxxing.org/api/forum/topics: public forum topic list
Contact
Email support@healthmaxxing.org for API documentation and product questions.