Add get page content endpoint to API reference

[mintlify]

Summary

Documents the new Get page content API endpoint (POST /v1/page/{domain}) that retrieves the full text content of a documentation page by its path.

This endpoint complements the existing Search documentation endpoint — after finding pages via search, you can now fetch their complete content programmatically.

Changes

• Added the endpoint definition to the OpenAPI spec (discovery-openapi.json)
• Created the api/assistant/get-page-content.mdx reference page
• Added the page to the Assistant navigation group in docs.json
• Updated api/introduction.mdx to list the new endpoint, reference it in the custom integrations use case, and include it in the assistant API key scope

Triggered by

A new discovery endpoint for fetching full page content was added to the Mintlify server.

---

Note

Low Risk
Low risk: this PR only updates documentation/navigation and the OpenAPI spec, with no runtime code changes. The main risk is incorrect API contract details (path/body/response) or broken docs links if the endpoint spec is wrong.

Overview
Documents a new endpoint POST /v1/page/{domain} to retrieve full text content for a page (intended to be used after Search documentation).

Adds a new reference page api/assistant/get-page-content.mdx, registers the endpoint in discovery-openapi.json (request includes page; responses include page + content, with a 404 error shape), and updates api/introduction.mdx + docs.json navigation to list it and include it under the assistant API key scope.

^{Written by Cursor Bugbot for commit f01aebe. This will update automatically on new commits. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
mintlify	🟢 Ready	View Preview	Mar 30, 2026, 10:27 PM

[ethanpalm]

lgtm! Is there a 500 response too? Can add as a follow up if needed.

[densumesh]

Will add as a followup! there should not be a 500