| Issue 605: | saved search API call | |
| 3 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
Hi -
I found the discussion [1] but couldn't find an open issue for it.
Minimally it would be nice if a users saved searches were available from
something like the user show method [2]. e.g.
<user>
<id>48833</id>
<name>Bryan Clark</name>
<screen_name>clarkbw</screen_name>
<saved_searches>
<saved_search>
<id>382</id>
<query>#twitter-api</query>
</saved_search>
</saved_searches>
... truncated ...
</user>
Not sure that looks right since its a couple levels deep but it has the
right amount of stuff to be able to store searches for clients.
I haven't seen any other discussion on a URL pattern or API calls for
actually working with saved searches.
Thanks for reading!
[1]
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/552ce2e9ce1d43da/edeccfc18edba22f
[2] http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show
|
||||||||||||
,
May 27, 2009
I'm working with a member of the User Experience team to get this added.
Status: Accepted
Owner: m...@twitter.com Labels: Component-REST |
|||||||||||||
,
Jun 02, 2009
Branch from User Experience completed and I've begun working on the API enhancements. |
|||||||||||||
,
Jun 04, 2009
(No comment was entered for this change.)
Status: Fixed
|
|||||||||||||
|
|
|||||||||||||