-
Notifications
You must be signed in to change notification settings - Fork 464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extra Parameters in Call Update #699
Comments
Hi @jon-sully , The update method has documentation
|
Hey there! Yes, I see that — but my understanding of the intention behind the Twilio SDK when it was written is that leaving it as I would think that if I have a Call resource saved and set on the back-end and a request comes in to the back end with Either way, since I'm specifically not passing a value for that particular key, I'd have expected it to not be present in the ultimate POST the SDK generates (issue 1.) and, even if it is, since it's sent with an empty value, I'd expect the back end to not overwrite my existing |
Issue Summary
Extra parameters are being sent along in my Call Updates — in particular,
StatusCallbackMethod
,Method
, andFallbackMethod
are all being sent to Twilio with the values of"POST"
even though I didn't specify them in my actualcalls(id).update( ... )
call.This wouldn't be a big deal except that I think by specifying the method for any of these endpoints, the actual URL stored for them gets reset. So my incoming calls, which had a Status Callback URL set by the TwiML App assigned to that phone number, were having their Status Callback URLs reset any time I used the Call Update API.
Steps to Reproduce
Code Snippet
Exception/Log
Completed parameter was sent but so were the other parameters.
Technical details:
(Twilio Ticket 15197987)
The text was updated successfully, but these errors were encountered: