ID: 17694
Comment by: steve@twitpic.com
Reported By: steve at twitpic dot com
Summary: Support for users/lookup, geo/search, and geo/id
Status: Open
Type: Feature/Change Request
Package: Services_Twitter
Operating System: FreeBSD
Package Version: 0.6.2
PHP Version: Irrelevant
Roadmap Versions:
New Comment:
Here is the patch- the "Add patch" system is not letting me upload
patch.txt for whatever reason.
239a240,245
<endpoint name="lookup" method="GET" auth_required="true"
min_args="1">
<formats>xml,json</formats>
<param name="user_id" type="string" required="false"/>
<param name="screen_name" type="string"
required="false"/>
<param name="include_entities" type="boolean"
required="false"/>
</endpoint> 471a478
<param name="result_type" type="string" required="false"/>
502c509,527min_args="1">
<formats>xml,json</formats>
<param name="user_id" type="string" required="false"/>
<param name="screen_name" type="string"
required="false"/>
<param name="include_entities" type="boolean"
required="false"/>
</endpoint> 471a478
<param name="result_type" type="string" required="false"/>
<
---
<!-- Geo API Methods -->
<category name="geo">
<endpoint name="search" method="GET" min_args="1"
auth_required="false">
<formats>json</formats>
<param name="lat" type="lat"
required="false"/>
<param name="long" type="long"
required="false"/>
<param name="query" type="string"
required="false"/>
<param name="ip" type="string"
required="false"/>
<param name="granularity" type="string"
required="false"/>
<param name="accuracy" type="string"
required="false"/>
<param name="max_results" type="integer"
required="false"/>
<param name="contained_within" type="string"
required="false"/>
<param name="autocomplete" type="boolean"
required="false"/>
</endpoint>
<endpoint name="id" method="GET" auth_required="true"
routing="/geo/id/:place_id">
<formats>json</formats>
<param name="place_id" type="string"
required="true"/>
</endpoint>
</category>
<category name="geo">
<endpoint name="search" method="GET" min_args="1"
auth_required="false">
<formats>json</formats>
<param name="lat" type="lat"
required="false"/>
<param name="long" type="long"
required="false"/>
<param name="query" type="string"
required="false"/>
<param name="ip" type="string"
required="false"/>
<param name="granularity" type="string"
required="false"/>
<param name="accuracy" type="string"
required="false"/>
<param name="max_results" type="integer"
required="false"/>
<param name="contained_within" type="string"
required="false"/>
<param name="autocomplete" type="boolean"
required="false"/>
</endpoint>
<endpoint name="id" method="GET" auth_required="true"
routing="/geo/id/:place_id">
<formats>json</formats>
<param name="place_id" type="string"
required="true"/>
</endpoint>
</category>
Previous Comments:
------------------------------------------------------------------------
[2010-08-11 15:19:46] steve_twitpic
Description:
------------
We use Services_Twitter extensively at Twitpic and wanted to
push some
of the API endpoints that we added back to you.
users/lookup - http://dev.twitter.com/doc/get/users/lookup
geo/search - http://dev.twitter.com/doc/get/geo/search
geo/id/ - http://dev.twitter.com/doc/get/geo/id/:place_id
NOTE: I had to add user_id and screen_name as type "string"
and not
"id_or_screenname" because these parameters take a CSV list
of ids or
screenames (you can pull up to 100 users at a time with the
API call).
There may be a better way to implement this, but it was the
easiest way
for us.
Test script:
---------------
$twitter = new Services_Twitter;
$twitter->users->lookup(array('user_id' => '12345'));
$twitter->geo->search(array('lat'=>90, 'long'=>90));
$twitter->geo->id(array('place_id' => 'abcdef123456'));
------------------------------------------------------------------------