Repository navigation
Align the 2.17 audience and dynamic content endpoints with what the API does - #755
Open
markdennis22 wants to merge 1 commit into
Open
markdennis22 wants to merge 1 commit into
markdennis22 wants to merge 1 commit into
Conversation
…API does Corrects the role predicate examples and the predicate value type, documents the error responses as the API sends them, notes the PATCH route and HTML-escaped names, and adds the accepted OAuth scopes to each operation. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This branch has not been deployed
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.
Why?
The 2.17 spec for the audience and dynamic content endpoints didn't match the API. The role predicate examples showed values the API never returns,
predicate.valuewas typed as a string, and several error responses were missing or worded differently from what the API sends. Only the 2.17 spec changes, and the SDKs aren't generated from 2.17, so they are unaffected.How?
Corrects the audience and dynamic content endpoints and schemas to match the API's current behaviour, and adds the OAuth scopes each endpoint accepts to its description.
Generated with Claude Code