POST geo/place not working properly; doc is incorrect


#1

https://dev.twitter.com/docs/api/1.1/post/geo/place

POST geo/place

First, the doc appears wrong. The example request should be pointing to geo/place.json, not geo/create.json (I get a “Sorry, that page does not exist” if I try to use create.json).

Then, even if I use geo/place.json I can’t get a correct response, even when using Twitter’s OAuth tool to generate the curl request, as shown (I removed any keys/tokens that were included explicitly):

curl --request 'POST' 'https://api.twitter.com/1.1/geo/place.json' --data 'contained_within=5e3152ed22b23547&lat=[lat]&long=[long]&name=Cool+Place&token=[token from similar_places]' --header 'Authorization: OAuth oauth_consumer_key="[]", oauth_nonce="[]", oauth_signature="[]", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1371672203", oauth_token="[]", oauth_version="1.0"' --verbose

I am using the token received from the similar_places.json call as outline in the doc. I keep getting “Could not authenticate you (32).”

What am I doing wrong?


#2

Just as a follow up, it’s not an OAuth problem as I’m successfully able to GET similar_places.json and obtain the token.

curl --get 'https://api.twitter.com/1.1/geo/similar_places.json' --data 'lat=[lat]&long=[long]&name=Cool+Place' --header 'Authorization: OAuth oauth_consumer_key="[]", oauth_nonce="[]", oauth_signature="[]", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1371673062", oauth_token="[]", oauth_version="1.0"' --verbose

#3

update: I tried getting this POST to work for a good hour or so, then with no changes that I knew of, it started working on its own. The doc is still weird, but the call appears to work now. :confused:


#4

Hi Cahlan,

POST geo/place endpoint will be retired. Please read the discussion here: https://dev.twitter.com/discussions/22452

Regards