Conversation
….ai T7197 Regenerated from the production /docs-json. Every operation now declares how it authenticates: bearerAuth with the required token scopes in its description, cookieAuth plus x-excluded for session-only routes (Mintlify leaves those out of the API reference), or no security for public routes. Compared with the previous spec: 286 endpoints become visible (routine, composio integrations, chat archive, admin integrity, base personal order, and other routes added since March), 80 session-only endpoints that an access token could never call are excluded, and 11 registry entries that never matched a real route are replaced by their corrected method or path. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Refreshes
swagger.jsonfrom the production OpenAPI document (https://app.teable.ai/docs-json), which now carries the auth-mode annotations shipped in teable-ee (T7197):x-excludedmarks session-only routes an access token can never call; Mintlify leaves them out of the API reference.security: []marks public routes.Compared with the previous spec
The excluded endpoints were never callable with an access token, so documenting them was misleading. If any of them should be opened to tokens, that is a backend change (
@TokenAccess()), not a docs one.Verification
mintlify openapi-check swagger.json: valid.mintlify broken-links: only pre-existing image links underarchive/.mintlify devpreview: API reference renders; the one in-content link into the reference (api-reference/automation/put-base-workflow-action) still resolves.🤖 Generated with Claude Code