Skip to content
The Docs Report
Tuesday, November 17, 2026NewsletterRSS

Fumadocs API Playground Adds OAuth Device Flow and a Stricter Proxy

fumadocs-openapi 12.5.0 adds PKCE, OpenID Connect and device authorization to the API playground. Its proxy now strips cookies and CORS headers.

3 min read

FumadocsOpen sourceAPI referenceSecurity

Product photo of a padlock on a cobalt blue, teal and violet gradient

The Fumadocs API playground can now sign in through OAuth 2.0 device authorization, OpenID Connect and PKCE, according to the Oct. 15 release notes for fumadocs-openapi 12.5.0. The same release makes the built-in request proxy much stricter by default.

New sign-in methods join the playground

The playground now supports OAuth 2.0 device authorization, OpenID Connect and PKCE, the Proof Key for Code Exchange extension. OAuth requests that use a client secret or the device flow go through proxyUrl when one is set, and the authorization server must be listed in allowedOrigins. The OAuth panel remembers the client ID.

Playgrounds on the same page now share auth values. A mutualTLS scheme no longer sends an Authorization header. Headless users get useOpenIdConnectFlows(), new return values from usePlaygroundAuth() and extra options on requestOAuthToken().

The proxy drops cookies and CORS headers

createProxy() no longer needs an allowedOrigins list. Without one, the release notes say, the proxy accepts any public origin and refuses private-network hosts on Node.js and Deno. It does not forward the site’s cookies or the response’s Set-Cookie headers. It strips headers that could affect the site, and proxied responses cannot run scripts on it.

Redirects to another origin drop the Authorization, Proxy-Authorization and Cookie headers. All Access-Control-* response headers are removed. Upstream statuses outside 200 to 599 now return 502 instead of 500, and requests abort when the client disconnects.

Example panels and internal APIs change

Example requests and responses were redesigned. Selects replace tabs, a Schema switch shows the JSON Schema for a response, and webhook examples use sections. The release fixes inline code samples with a function source that rendered empty, and a sticky example column that overlapped the header in Notebook layouts.

Several internal APIs are now hidden: generatePythonObject(), InternalOpenAPIMeta, _getWatchPaths(), the Awaitable and DistributiveOmit types, usePlaygroundAuth().subscribe() and the CSS files under fumadocs-openapi/css/ other than preset.css. The notes do not label any change as breaking.

Other packages tightened the same rule

The Oct. 16 releases of the GraphQL and AsyncAPI packages, @fumadocs/graphql 0.3.5 and @fumadocs/asyncapi 0.4.6, refuse schema IDs that are not listed in input. In fumadocs-openapi 12.5.1, getSchema() does the same. The OpenAPI release also made @fumari/stf and @fumadocs/json-schema caret ranges, so UI installed through the Fumadocs CLI can share one copy.

Key takeaways

  • fumadocs-openapi 12.5.0 adds OAuth 2.0 device authorization, OpenID Connect and PKCE to the playground.
  • createProxy() now works without allowedOrigins but drops cookies, Set-Cookie and all Access-Control-* headers.
  • Cross-origin redirects lose Authorization, Proxy-Authorization and Cookie headers.
  • The GraphQL, AsyncAPI and OpenAPI packages now reject schema IDs missing from input.

The take

We think the proxy change matters more than the new sign-in flows. A playground proxy forwards a reader’s requests to someone else’s server. A proxy that also forwarded the site’s own cookies could hand a reader’s session to a third party. Dropping cookies and CORS headers by default closes that door.

The practical step is small. Add the authorization server for any OAuth flow to allowedOrigins. The new flows route through it. Then test any page that relied on cookies passing through the proxy. Version 12.5.0 no longer forwards them.