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

GitBook Now Expires New API Tokens After 90 Days by Default

GitBook's Nov. 11 update gives new personal API tokens a 90-day life, lets AI Assistant analytics filter by cited page and copies table cells.

3 min read

GitBookSecurityAPI

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

New personal API tokens in GitBook now stop working after 90 days unless the person creating them picks another date, GitBook said in its Nov. 11 changelog. The creator can pick 7, 30, 60 or 90 days, a custom date or no expiration.

Never is still an option

Choosing no expiration keeps a token active until it is deleted, and GitBook now shows a reminder saying so. The company said it recommends that setting only for long-running integrations that are hard to update. It also told users to store tokens somewhere secure and delete them when they are no longer needed.

Scripts that create tokens through the API can set the end date with a new expiresAt field.

GitBook framed the change as risk reduction: tokens that expire on their own are “one less thing to keep track of,” and they limit the damage if a token is shared or forgotten, the changelog said.

Docs teams can now search the questions visitors ask GitBook’s AI Assistant by text and filter the report by the pages its answers cite. The API exposes the same filter as citedPage. That lets a writer see what readers ask about one page without scrolling the whole list, GitBook said.

On published sites, the assistant now reminds visitors not to share sensitive personal information, and it does not recommend competitors when a visitor asks for alternatives, according to the changelog.

Smaller changes

  • Editors can select a range of table cells and copy, cut or paste them. A paste that runs past the table’s edge grows the table.
  • GitBook Agent conversations can be renamed.
  • Sites behind authentication serve robots.txt without asking for a sign-in.
  • The docs MCP server for published sites finds pages by their .md URLs.
  • File uploads work again, including imported Word and Markdown files.

Key takeaways

  • New personal API tokens expire after 90 days unless the creator picks 7, 30 or 60 days, a custom date or never.
  • The API sets token lifetimes with expiresAt.
  • AI Assistant analytics can search questions and filter by cited page, also via citedPage in the API.
  • The published-site assistant will not point visitors to competitors.

The take

We think the 90-day default is the right call. A token nobody remembers is the one nobody revokes, and an end date turns that forgotten secret into a dead string.

The cost falls on integrations. A sync job or CI pipeline built on a 90-day token will fail quietly the day it expires. So the default only helps if teams pair it with a reminder to rotate.

The competitor rule cuts the other way. By design, the assistant now withholds an answer a visitor asked for. That suits a company’s docs site, but readers should know its replies are not neutral advice.

Before relying on the new default, we’d list every GitBook token in use, set each integration’s expiry on purpose and put the renewal date on a calendar.