Twitter API
    Twitter API
    • /account/settings.json
      GET
    • /account/settings.json
      POST
    • /account/update_delivery_device.json
      POST
    • /account/update_profile.json
      POST
    • /account/update_profile_background_image.json
      POST
    • /account/update_profile_colors.json
      POST
    • /account/update_profile_image.json
      POST
    • /application/rate_limit_status.json
      GET
    • /blocks/create.json
      POST
    • /blocks/destroy.json
      POST
    • /blocks/ids.json
      GET
    • /blocks/list.json
      GET
    • /direct_messages.json
      GET
    • /direct_messages/destroy.json
      POST
    • /direct_messages/new.json
      POST
    • /direct_messages/sent.json
      GET
    • /direct_messages/show.json
      GET
    • /favorites/create.json
      POST
    • /favorites/destroy.json
      POST
    • /favorites/list.json
      GET
    • /followers/ids.json
      GET
    • /friends/ids.json
      GET
    • /friendships/create.json
      POST
    • /friendships/destroy.json
      POST
    • /friendships/incoming.json
      GET
    • /friendships/lookup.json
      GET
    • /friendships/outgoing.json
      GET
    • /friendships/show.json
      GET
    • /friendships/update.json
      POST
    • /geo/id/{place_id}.json
      GET
    • /geo/places.json
      POST
    • /geo/reverse_geocode.json
      GET
    • /geo/search.json
      GET
    • /geo/similar_places.json
      GET
    • /help/configuration.json
      GET
    • /help/languages.json
      GET
    • /help/privacy.json
      GET
    • /help/tos.json
      GET
    • /lists/create.json
      POST
    • /lists/destroy.json
      POST
    • /lists/list.json
      GET
    • /lists/members.json
      GET
    • /lists/members/create.json
      POST
    • /lists/members/create_all.json
      POST
    • /lists/members/destroy.json
      POST
    • /lists/members/destroy_all.json
      POST
    • /lists/members/show.json
      GET
    • /lists/memberships.json
      GET
    • /lists/show.json
      GET
    • /lists/statuses.json
      GET
    • /lists/subscribers.json
      GET
    • /lists/subscribers/create.json
      POST
    • /lists/subscribers/destroy.json
      POST
    • /lists/subscribers/show.json
      GET
    • /lists/subscriptions.json
      GET
    • /lists/update.json
      POST
    • /saved_searches/create.json
      POST
    • /saved_searches/destroy/{id}.json
      POST
    • /saved_searches/list.json
      GET
    • /saved_searches/show/{id}.json
      GET
    • /search/tweets.json
      GET
    • /statuses/destroy/{id}.json
      POST
    • /statuses/home_timeline.json
      GET
    • /statuses/mentions_timeline.json
      GET
    • /statuses/oembed.json
      GET
    • /statuses/retweet/{id}.json
      POST
    • /statuses/retweets/{id}.json
      GET
    • /statuses/show/{id}.json
      GET
    • /statuses/update.json
      POST
    • /statuses/update_with_media.json
      POST
    • /statuses/user_timeline.json
      GET
    • /trends/available.json
      GET
    • /trends/closest.json
      GET
    • /trends/place.json
      GET
    • /users/contributees.json
      GET
    • /users/contributors.json
      GET
    • /users/lookup.json
      GET
    • /users/report_spam.json
      POST
    • /users/search.json
      GET
    • /users/show.json
      GET
    • /users/suggestions.json
      GET
    • /users/suggestions/{slug}.json
      GET
    • /users/suggestions/{slug}/members.json
      GET

      /geo/search.json

      GET
      /geo/search.json
      Search for places that can be
      attached to a statuses/update. Given a latitude and a longitude pair, an IP address, or a name, this
      request will return a list of all the valid places that can be used as the place_id when updating a
      status.
      Conceptually, a query can be made from the user's location, retrieve a list of places, have the user
      validate the location he or she is at, and then send the ID of this location with a call to POST
      statuses/update.
      This is the recommended method to use find places that can be attached to statuses/update. Unlike
      GET geo/reverse_geocode which provides raw data access, this endpoint can potentially re-order
      places with regards to the user who is authenticated. This approach is also preferred for
      interactive place matching with the user.
      Request Request Example
      Shell
      JavaScript
      Java
      Swift
      curl --location --request GET 'https://api.twitter.com/1.1/geo/search.json'
      Response Response Example
      {}

      Request

      None

      Responses

      🟢200Successful Response
      application/json
      Body
      object {0}
      Modified at 2022-09-10 16:58:08
      Previous
      /geo/reverse_geocode.json
      Next
      /geo/similar_places.json
      Built with