[EPMTIOOPS-18112] [API Documentation] Features: Missed endpoint for get features under section - #35
Merged
aliaksandr5filippov merged 2 commits intoFeb 27, 2026
Conversation
…et features under section
…ow to work with 'sections' on guides.test.io
razvan-pavel
approved these changes
Feb 26, 2026
egvlasov
approved these changes
Feb 26, 2026
aliaksandr5filippov
deleted the
EPMTIOOPS-18112/api_features_wo_sections
branch
February 27, 2026 05:01
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
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.
EPMTIOOPS-18112
[API Documentation] Features: Missed endpoint for get features under section
https://jiraeu.epam.com/browse/EPMTIOOPS-18509
[S][API Documentation] Create clear documentation how to work with 'sections' on guides.test.io
Problem:
GET /products/{product_id}/featuresimplied that products with sections must use the section-scoped endpoint, causing confusion about when each endpoint should be used.Solution:
GET /products/{product_id}/featuresreturns all features regardless of whether sections are enabled, and thatGET /products/{product_id}/sections/{section_id}/featuresis an optional alternative for retrieving features scoped to a particular section.Before fix:
After fix: