Add documentation for API Members #6646
Merged
Conversation
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
sofietoft
reviewed
Nov 12, 2024
15/umbraco-cms/reference/content-delivery-api/protected-content-in-the-delivery-api/README.md
Outdated
Show resolved
Hide resolved
…t-in-the-delivery-api/README.md Co-authored-by: sofietoft <[email protected]>
|
Fine by me, @sofietoft 😄 |
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.
Description
Added documentation for the new API Members feature in V15, which is all about accessing protected content from the Delivery API in a server-to-server context.
Notice that the included code sample is a little more complex than strictly need be. This is to ensure we promote best practice approaches to token reuse, in case readers "copy & own" the sample code later on.
I have also added a cross reference from the existing article about accessing protected content from the Delivery API in a client-to-server context.
Type of suggestion
Product & version (if relevant)
V15
Deadline (if relevant)
Not urgent - but ideally at V15 launch or shortly thereafter (please prioritise the API Users article above this one, though).