Changelog

OAuth logout endpoint

You can now configure a logout URL for OAuth authentication. When a user clicks Logout, Fern redirects them to your OAuth provider’s logout endpoint to end their session, in addition to clearing the local session cookie. To set this up, send your logout URL (e.g., https://<your-oauth-tenant>/oauth2/logout) to Fern alongside your other OAuth client details.

“Edit this page” with Fern Editor

The “Edit this page” button can now open Fern Editor in addition to linking to GitHub. When you set the launch mode to dashboard, clicking the button gives users the choice between editing the page in Fern Editor or viewing the source on GitHub. This is especially useful for internal docs sites where most viewers are also editors.

Collaborative editor sessions

You can now view and edit your teammates’ Fern Editor sessions. If a teammate creates an editor session, you can open their session from the Dashboard and commit changes directly to their PR. This makes it easy to adjust copy or fix content without switching to GitHub.

Learn more about the Fern Editor.

OpenAPI spec endpoints

Your Fern docs site now serves your raw OpenAPI 3.1 specification at /openapi.json and /openapi.yaml. Download it for SDK generation, contract testing, or importing into tools like Postman. The spec is also linked from your site’s llms.txt, so AI coding assistants can discover and use it automatically.

Edit site logo, favicon, and title from the editor

You can now update your site’s logo, favicon, and title directly from Fern Editor — no need to edit configuration files manually. Navigate to site settings in the editor to make changes visually.

Link to API endpoints with api: syntax

Link to API endpoints by HTTP method and path using the api: link syntax, instead of hardcoding URL slugs. Fern resolves these links to the correct endpoint URL at build time.

1
[Create a payment](api:POST/v2/payments)

This works in Markdown pages, OpenAPI description fields, and Fern Definition docs fields.

Steps TOC depth follows heading level

When using <Steps toc={true}> with markdown heading syntax, step entries now appear in the table of contents at the depth that matches their heading level — ## headings at depth 2, ### headings at depth 3.

POST support for JWT callback

The JWT callback endpoint (/api/fern-docs/auth/jwt/callback) now accepts POST requests with application/x-www-form-urlencoded body in addition to GET requests with query parameters. POST avoids exposing JWT tokens in URLs and server logs.

API key injection for self-hosted docs

Self-hosted deployments support API key injection via environment variables. Enable FERN_API_KEY_INJECTION_ENABLED to show a Login button in the API Explorer without requiring login for the entire site. Use FERN_AUTH_ALLOWLIST and FERN_AUTH_DENYLIST to control page-level access.

Multiple API keys and per-environment keys

API key injection supports multiple API keys and per-environment credentials. Provide multiple keys as a JSON-encoded array in bearer_token, and use env_state to set different credentials per environment with substring matching.

Customize GraphQL API Reference layout

Control how GraphQL operations appear in the sidebar using the operation keyword in your docs.yml layout. Order operations, set custom titles and slugs, hide operations, and group them into sections.

1
navigation:
2
  - api: GraphQL API Reference
3
    layout:
4
      - section: Plants
5
        contents:
6
          - operation: QUERY getPlant
7
            title: Get plant details
8
          - operation: MUTATION createPlant