Add reference to Audiences for filtering API endpoints in API Reference docs #397
+3
−1
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
Contributor
Contributor
devalog
approved these changes
Aug 11, 2025
Collaborator
devalog
left a comment
devalog
left a comment
There was a problem hiding this comment.
Thank you so much for contributing! To avoid repeating information that is already covered in the standalone Audiences page, I've removed the new section you created and just expanded the description (based on your original change) in the table instead.
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.
This PR adds a short mention of using Audiences to include only specific API endpoints in the API Reference documentation.
While the
audiencesproperty is mentioned in the configuration table, its primary use case for filtering endpoints isn't highlighted.This change improves the user journey by proactively addressing the common question, "How do I show only some of my endpoints?" at a logical point in the documentation.