TE-12682: Document + / %2B handling in form-encoded API bodies#2895
Draft
subhams-svg wants to merge 1 commit intoLambdaTest:stagefrom
Draft
TE-12682: Document + / %2B handling in form-encoded API bodies#2895subhams-svg wants to merge 1 commit intoLambdaTest:stagefrom
subhams-svg wants to merge 1 commit intoLambdaTest:stagefrom
Conversation
Adds a new section to the KaneAI API Testing docs explaining how + and %2B are processed differently between manual entry in the body editor and pasted cURL commands, so users can correctly send literal plus characters (e.g. phone-number prefixes) to form-urlencoded endpoints. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
subhams-svg
force-pushed
the
te-12682-form-encoded-special-chars-doc
branch
from
2bc7b82 to
ffe1dfa
Compare
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
1 participant
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.
Summary
Adds a new section to KaneAI - API Testing explaining how
+and%2Bare processed differently between manual entry in the request body editor and pasted cURL commands. This closes the documentation gap flagged on TE-12682, where customer phone-number values like+917777711791were being decoded to a space on the wire (form-urlencoded spec behavior) and producing "Invalid Phone number" responses.The new content covers:
+917777711791and%2B917777711791are accepted; the response panel shows the resolved value.+in-dis decoded to space (spec-correct); to send a literal+, encode as%2B.%2Bfor a phone-number value.No other content is modified; existing sections after the new one are simply renumbered (3→4, 4→5, …, 7→8).
Test plan
pnpm start— new section renders correctly between Adding a Curl Command and Validating API Response on KaneAI, tables display cleanly, and the code block renders.🤖 Generated with Claude Code