So I’m working on “favoriting” support for my private experimental Twitter client. I noticed that the REST API randomly denies to accept valid tweet IDs.
From the “example curl” request:
curl --request ‘POST’ ‘https://api.twitter.com/1.1/favorites/create.json’ --data ‘id=243138128959913986’ --header ‘Authorization: OAuth oauth_consumer_key="…", oauth_nonce="…", oauth_signature="…", oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1385059024”, oauth_token="…", oauth_version=“1.0”’ --verbose
Works, returns the tweet (as JSON).
curl --request ‘POST’ ‘https://api.twitter.com/1.1/favorites/create.json’ --data ‘id=403592186656071680’ --header ‘Authorization: OAuth oauth_consumer_key="…", oauth_nonce="…", oauth_signature="…", oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1385059024”, oauth_token="…", oauth_version=“1.0”’ --verbose
Fails, returns:
{“errors”:[{“message”:“Could not authenticate you”,“code”:32}]}
The tweet with the ID 403592186656071680 is public and existing though, and I’m not blocked.
I’d assume the REST API can’t handle “too large” IDs? Or any other clue?
