Skip to content

fix: pre-fill Accept & Content-Type headers in API Docs playground - #4

Open
Nitesh-BE wants to merge 16 commits into
masterfrom
newFix
Open

fix: pre-fill Accept & Content-Type headers in API Docs playground#4
Nitesh-BE wants to merge 16 commits into
masterfrom
newFix

Conversation

@Nitesh-BE

Copy link
Copy Markdown
Collaborator

Summary

  • Content-Type header pre-filled — Added Content-Type: application/json as an explicit header parameter with example: application/json to all 90 endpoints that accept a JSON request body. Users no longer need to manually type it in the API playground.
  • Accept header gap fixed — Added missing Accept: application/json header parameter to POST /v1/messenger/export (was the only endpoint without it; all 162 other endpoints already had it).
  • Restored mcp/tools/listings pages — Re-added 5 mcp/tools/listings/*.mdx pages (overview, get-listing, get-listing-location-status-report, get-listing-category-list, get-product-listing-list) that were accidentally removed in a previous session's commits.

Notes on /mcp redirect

The redirect rule (/mcp/mcp/introduction) added in PR #3 already exists in docs.json and works correctly in local Mintlify dev. On the hosted Mintlify site, the /mcp path is served by Mintlify's own infrastructure-level MCP manifest endpoint (their AI docs feature), which takes precedence before any app-level redirect can fire. This is a Mintlify platform behaviour — resolving it requires either a Mintlify dashboard setting or contacting Mintlify support to disable/reconfigure their built-in /mcp route for this project.


Generated by Claude Code

Nitesh-BE added 16 commits July 16, 2026 17:01
…ict (1/3)

Mintlify v2 intercepts GET /mcp at CDN level to serve its own MCP manifest
JSON — no redirect rule in docs.json can override it. Moving MCP documentation
from mcp/ to mcp-server/ eliminates the path conflict entirely so the tab
serves real HTML pages. All internal cross-links updated accordingly.
…e mcp/tools/listings pages

- Add Content-Type: application/json header parameter (with pre-filled example) to all 90
  endpoints that have a JSON request body, so users don't need to type it manually in the
  API playground
- Add missing Accept: application/json header parameter to POST /v1/messenger/export
  (was the one endpoint without it)
- Restore mcp/tools/listings/*.mdx pages that were accidentally removed in previous commits
- Add Content-Type: application/json header parameter (example pre-filled) to
  all 90 endpoints with a JSON request body so users don't need to type it
  manually in the API Docs playground
- Add missing Accept: application/json header parameter to POST /v1/messenger/export
  (was the only endpoint without it; all other 162 endpoints already had it)
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