docs: clarify client-side phoneNumber requirements per token type (#158) - #205
Merged
stroncoso merged 1 commit intoJul 19, 2026
Conversation
docs: clarify client-side phoneNumber requirements per token type (camaraproject#158) Signed-off-by: Deepak Jaiswal <deepak.jaiswal1@t-mobile.com>
deepakjaiswal1
requested review from
pradeepachar-mavenir,
stroncoso and
teikuran
as code owners
July 15, 2026 01:00
teikuran
approved these changes
Jul 15, 2026
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
3 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.
docs: clarify client-side phoneNumber requirements per token type (#158)
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
Follow-up to #187. Makes the client-side requirements for
phoneNumberexplicit: with a three-legged access token the API consumer MUST NOT includephoneNumberin the request body, and with a two-legged token the API consumer MUST include it. ThephoneNumberfield description and thePOST /sessionsdescription now separate "Client requirements" from "Server behaviour", so the client obligation is stated directly rather than left implicit in the422error codes.Which issue(s) this PR fixes:
Refs #158
Special notes for reviewers:
No behavioural change. This is a wording/clarity update addressing internal feedback on #187 (thread from @takakura and Santiago Troncoso). The rules are unchanged; they are now stated from the client's perspective as well as the server's.
Changelog input