yes i too encountered this (both status/destroy and direct_messages/destroy
are giving 400 error but the status gets deleted successfully. The response
text says something like "somehow we could not delete this tweet."
On Wed, Aug 19, 2009 at 3:38 PM, deepikagupta <deepikaggu...@gmail.com>wrote:
> I am facing an issue with statuses/destroy API call. It returns 400
> (bad request) even though mentioned tweet id is delered sucessfully.
> The method was working fine few days back but started gicing trouble
> Anyone having same trouble? Is anything wrong with this API call?