Skip to content

Add support API and compatibility check endpoints#296

Open
mintlify[bot] wants to merge 2 commits into
mainfrom
mintlify/token-refresh-api-1775278047
Open

Add support API and compatibility check endpoints#296
mintlify[bot] wants to merge 2 commits into
mainfrom
mintlify/token-refresh-api-1775278047

Conversation

@mintlify
Copy link
Copy Markdown
Contributor

@mintlify mintlify Bot commented Apr 4, 2026

Summary

  • Added new Support API page documenting the POST /api/support/heal-token (auto-generates gateway tokens) and GET /api/support/diagnostics (platform health snapshot) endpoints
  • Added POST /api/openclaw/ensure-compatibility endpoint to the Maintenance API page for OpenClaw 2026.4.2 compatibility checks
  • Updated the API reference overview with the three new endpoints
  • Added a troubleshooting entry for gateway token issues, referencing the auto-heal and diagnostics endpoints
  • Updated navigation to include the new support page

Open in Devin Review

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 4, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
mintlify-docs Ready Ready Preview, Comment Apr 25, 2026 11:25am

Request Review

Copy link
Copy Markdown

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 1 potential issue.

View 2 additional findings in Devin Review.

Open in Devin Review

Comment thread api-reference/support.mdx
Comment on lines +1 to +4
---
title: Support API
description: "Token auto-healing, diagnostics, and self-service support endpoints"
---
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 New support page not added to docs.json navigation

The new api-reference/support.mdx page is created but not registered in the navigation.groups array in docs.json. The "API Reference" group (docs.json:95-183) lists all API reference pages, but "api-reference/support" is missing. This means the page will exist but be unreachable through the site's navigation menu — users can only access it via a direct URL.

Prompt for agents
The new file api-reference/support.mdx needs to be added to the navigation configuration in docs.json. In docs.json, find the "API Reference" group (around line 95) and add "api-reference/support" to the pages array. A logical placement would be near related endpoints like api-reference/health or api-reference/debug (around lines 122-138).
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant