API Explorer
Reduce "time to 200" by allowing users to make real calls to your API from right within the API Reference.
Fern’s API Explorer allows users to make authenticated requests to your API without ever leaving your documentation.
Fern will automatically populate the fields of the endpoint with the values set in your API specification.
The API Explorer supports all authentication schemes configured in your OpenAPI spec or in generators.yml, including multiple authentication schemes. When multiple schemes are available, the API Explorer automatically displays them in a dropdown menu, allowing users to select and configure their preferred authentication method before sending requests.
Once a user sets their authentication credentials, their credentials persist throughout their entire exploration session.
Authentication credentials are only stored client-side using cookies. No sensitive user information is collected or stored.
To automatically populate API keys for logged-in users, see API key injection.
When multiple server URLs are configured in OpenAPI, users can switch between environments (e.g., production and sandbox) from a dropdown in the API Explorer. The selected environment persists as they navigate between pages.
Users can also double-click the server URL to manually edit it, allowing for quick testing against custom environments or endpoints.
Here’s an example of the Flagright docs site with multiple server names configured.
For APIs that support WebSocket connections, the API Explorer includes a WebSocket-specific Playground. The WebSocket Playground also allows users to establish a connection with the API, and send/receive messages in real-time.
For OpenAPI specs, the API Explorer is enabled by default for all endpoints. You can disable it globally or per endpoint using the x-fern-explorer extension. This is commonly used to disable the Explorer for destructive operations, payment processing, or admin-only endpoints.