Fix array parameter serialization for tollfree verification requests #761
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.
The tollfree verification API was returning "Missing required parameter" errors for array parameters (
UseCaseCategories
andOptInImageUrls
) even when they were properly included in the request. This issue occurred specifically when using sub-accounts.The root cause was that array parameters were being serialized as repeated form parameters (
param=A¶m=B¶m=C
) instead of comma-separated strings (param=A,B,C
) which is the format expected by the Twilio API.Changes Made
TollfreeVerificationList#create
to serialize array parameters as comma-separated stringsTollfreeVerificationContext#update
to use the same serialization approachBefore (causing API errors):
After (working correctly):
The fix handles all edge cases correctly:
nil
and:unset
values are preservedFixes #674.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.