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

Zudoku Now Accepts Opaque OpenID Tokens and Parameterized Redirects

Zudoku 0.93.0, released Oct. 13, allows opaque OpenID access tokens, adds path parameters to redirects and sends existing subscribers to plan changes.

2 min read

ZudokuOpen sourceAPI reference

A brass skeleton key floating over a cherry red, orange and hot pink gradient

Zudoku, the open-source API documentation framework from Zuplo, now accepts opaque OpenID access tokens, according to its v0.93.0 release notes dated Oct. 13. The same release adds path parameters to dynamic redirects and routes existing subscribers into a plan-change flow at checkout.

Opaque tokens now work for sign-in

Zudoku’s OpenID authentication now allows opaque access tokens. These tokens carry no readable claims. A first-time contributor, @stayallive, made the change. API key requests that fail on an opaque token now get a clearer explanation. The Auth0 guide also now says the audience is optional for sign-in-only flows.

Redirects can carry path parameters

Dynamic redirects support path parameters. One rule can move a whole family of old URLs instead of needing an entry per page.

Checkout sends subscribers to plan changes

Existing subscribers who open /checkout now go into the plan-change flow instead of a new purchase.

Earlier releases tightened the framework

The v0.92.0 release, dated Oct. 8, adds a disableRequestBox option that hides the sidecar request box in the API reference. The v0.91.0 release, also from Oct. 8, makes plugins that define conflicting routes raise an error. It also wraps MDX tables in a scrollable container, adds SEO frontmatter for page titles and descriptions, and fixes code block titles, KaTeX display math and mobile navigation closing. PATCH now sorts before DELETE in the OpenAPI method order.

The unpublished draft of the next release on the same page reads OpenAPI enum descriptions from x-enum-descriptions and makes llms.txt use each page’s SEO description, matching the page head.

Key takeaways

  • Opaque OpenID access tokens are accepted as of Oct. 13.
  • Redirect rules can use path parameters.
  • Plugins with conflicting routes now fail loudly instead of silently.
  • disableRequestBox hides the request box.

The take

We think the route-conflict error matters more than its one-line entry suggests. A framework that lets two plugins claim the same URL picks a winner silently. The site owner finds out when a page shows the wrong content. An error at build time replaces that guess with a fact. Teams running Zudoku should upgrade and rebuild. If the build now fails, two of their plugins were already colliding.