Repository navigation
Hide the Backend API logs endpoints from the published reference - #133
Merged
Merged
Conversation
The /logs family (list, get, schemas) went public in the Backend API reference on 2026-09-22 before rate limiting and the API's stability posture were settled. This removes the Logs tag, the three /logs paths, and their schemas from every published BAPI version so the reference and generated SDKs stop advertising them while that work lands. The FAPI and Platform API changes from the same publish are kept. The endpoints themselves stay live; only the docs visibility changes. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Preview Links |
tmilewski
approved these changes
Sep 23, 2026
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
2 participants
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.
Why
The Backend API
/logsendpoints (GET /logs,GET /logs/{event_time_and_id},GET /logs/schemas) were published in the reference on 2026-09-22 via #132, ahead of two things we want in place first: rate limiting suited to agent-driven callers, and an explicit experimental marker, since the response shape is still expected to change. Within a day of publication we saw new customers start calling it, including agent loops with malformed pagination params.This takes the endpoints back out of the published reference so the docs and the generated SDKs stop advertising them until that work is done. The endpoints themselves remain live for the customers already using them.
What changed
Only the five
bapi/*.ymlfiles are touched. Each drops exactly the 637 lines that #132 added for the logs family: theLogstag, the three/logspaths, and theLog,LogWithPayload, andLogSchemaschemas. The FAPI and Platform API changes from #132 are untouched.Related
x-publicmarkers back so the next automated publish doesn't re-add them: clerk/clerk_go#22393🤖 Generated with Claude Code