Every page of our API docs in Markdown: View as Markdown, Copy page and what they are for

AI & Agents·· 14 views· 3 min read

The short answer: every page of the documentation also exists in Markdown, plain text with light formatting. At the top of each page there are two buttons: View as Markdown opens that version and Copy page copies it in one go. They are mainly for giving the documentation to an AI assistant or keeping it next to your code.

The two buttons

Button What it does
View as Markdown Opens the page in Markdown, at its own address ending in .md. For example, Get started with the API in Markdown.
Copy page Copies that same text to your clipboard, ready to paste elsewhere.

What it is for

1 Giving context to an AI assistant: paste the page into a conversation and ask for code, an explanation or a review. The assistant then works from the right text, not from memory.
2 Keeping it with your code: a copy of the area page you use, inside the project, helps whoever comes after you.
3 Reading outside the browser: in a text editor or a terminal, with no menus or buttons.
4 Seeing what changed: every version has its update date at the top; if you keep copies, you can compare one with another.

How it differs from the page

In the Markdown version What you get
Top The title, the description and the "Updated on" date.
Text The same as the page, with no menus, buttons or Playground.
Links Full addresses that lead to the Markdown versions of the other pages.
Area pages The guide followed by every operation, with examples in all four languages and the responses.
Reference One table per area, with the method, the path and what each operation does.
The Markdown versions do not show up in search engines. To send someone a link to read, use the normal page; Markdown is for pasting and for tools.
Want the list of every Markdown page at once? It is in the documentation llms.txt file: see llms.txt and AI tools.

Try it with the page you use most: open it and click View as Markdown.

Open the documentation

SEE ALSO

Our API docs and AI tools: the llms.txt file and giving an assistant the whole documentation

Summarise with AI and Share in our API docs: what the buttons do and when to trust the answer

Handing our API docs to a developer or agency: section links, Markdown and the specification

How our API documentation is organised: Get started, Areas, API reference and Playground

llms.txt: what it is, and whether it does anything for your site

RECOMMENDED PRODUCT

Web hosting with cPanel

Domain and SSL included, daily backups and the panel you already know. from $5.36/mo (3-year plan, with coupon)

See plans
Was this answer helpful? Your answer helps us improve this article.