PDF and Word export

Exports contain the real API documentation, not an empty box.

When a page is exported to PDF or Word, each Apifolio macro becomes a static version of the documentation:

API title, version and description;
servers and authentication methods;
one table of endpoints per section (method, path, summary);
endpoint details: parameters, request body fields, an example request body, responses and an example response.

The export follows the macro's filters (sections, paths, hidden deprecated endpoints) and its show/hide options.

Limits

To keep exports fast and reliable:

APIs with more than 250 endpoints (after filters) are exported as endpoint tables only. Narrow the macro to fewer sections to export full details.
Very large exports are shortened with a note at the end.

If a spec can't be read during export, the document shows a short note instead of failing.