When we delete a tweet natively and then try to reply to it via the api console, the reply gets posted on the platform as a ‘Tweet’. Is this behavior by design?
Example:
https://twitter.com/navya_adobe/status/796350982204424192 was deleted. When trying to reply to it via twitter api console using the ‘in_reply_to_status_id’ field,
Request URL being:
https://api.twitter.com/1.1/statuses/update.json?status=test%20deleted%20tweet&in_reply_to_status_id=796350982204424192&display_coordinates=false
it gets posted on the platform.(not as a reply, but as a tweet)
https://twitter.com/navya_adobe/status/816574352871276544
Is this the intended behavior? Any help would be appreciated.
This is expected behaviour, since there’s no Tweet left to reply to.
Note that in the future with the changes we are working on to simplify replies, an attempt to reply to a deleted Tweet will return an error, but this is not yet live.
