docs: add device identifier constraints per #513#576
Merged
rartych merged 4 commits intocamaraproject:mainfrom Jan 30, 2026
Merged
docs: add device identifier constraints per #513#576rartych merged 4 commits intocamaraproject:mainfrom
rartych merged 4 commits intocamaraproject:mainfrom
Conversation
Added guidelines for the inclusion of the `$.device` property in API responses based on request conditions, specifying scenarios for both API provider discretion and mandatory inclusion for 2-legged access tokens.
Kevsy
commented
Jan 19, 2026
Kevsy
commented
Jan 19, 2026
PedroDiez
reviewed
Jan 19, 2026
Co-authored-by: Pedro Díez García <pedro.diezgarcia@telefonica.com>
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
4 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.
Added guidelines for the inclusion of the
$.deviceproperty in API responses based on request conditions, specifying scenarios for both API provider discretion and mandatory inclusion for 2-legged access tokens.What type of PR is this?
What this PR does / why we need it:
Clarifies the
.featureconstraints that should be used where the$.deviceobject has been included in the request body.Which issue(s) this PR fixes:
Fixes #513
Does this PR introduce a breaking change?
Special notes for reviewers:
Changelog input
Additional documentation
This section can be blank.