I'm using the users/lookup.json API and passing a valid list of
user_ids that I retrieve from friends/ids (yes, there are 100).
I keep getting the response: No user matches for specified terms
when making the call, even though the list is valid and I have
inspected the request being sent.
Any
Hi,
I have read all the users/lookup related posts and also scoured the
internet looking for an appropriate example.I posted a question as a
reply on one but don't see it so I am hoping someone can help a
twitter api newbie.
I just want to get results from users/lookup. I am using Abraham's
Oauth
Try:
$userDeets = $connection-get('users/lookup' array('screen_name' =
'biz,twitterapi'));
That should work.
Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
http://abrah.amJust launched from Answerly http://answerly.com:
InboxQhttp://inboxq.comfor Chrome
@abraham
Before I post this as an issue is anyone else getting this problem.
When I lookup multi users by username I get correct information on the
user but the status supplied is an out of date in some cases.
Cheers
Darren
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
I can confirm that this happens whether the lookup is by screen_name or id.
Incidentally, any progress on Twitter's side? Way over a month now, and it
only seems to be getting worse.
Cheers,
Adrian
On Tue, Mar 22, 2011 at 1:18 AM, Nischal Shetty
nischalshett...@gmail.comwrote:
Anything on
Anything on this? It's been quite some time and user lookup I believe would
be used by a lot of apps.
-N
On 16 March 2011 05:46, Taylor Singletary taylorsinglet...@twitter.comwrote:
Still working on it, unfortunately. No ETA for a fix yet. I know it's an
aggravating bug for anyone who runs
Hi Taylor,
Not trying to be pushy or anything, but have you guys uncovered anything
related to this issue? It's still happening quite regularly for a couple of
weeks now.
Thanks,
Adrian
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter:
Still working on it, unfortunately. No ETA for a fix yet. I know it's an
aggravating bug for anyone who runs into it. Thanks for being patient.
Taylor
On Mar 15, 2011, at 5:09 PM, Adrian Petrescu apetr...@gmail.com wrote:
Hi Taylor,
Not trying to be pushy or anything, but have you guys
When using users/lookup with 100 random screen_names, I often get duplicate
records, as well as missing records for valid users that are not deleted,
suspended, or non-existent. Ive tested this with python-twitter as well as
twurl. The responses I receive are non-deterministic; different users are
Hi Kurt,
Thanks for the great detailed bug report. We're investigating this issue.
Taylor
@episod http://twitter.com/episod - Taylor Singletary - Twitter Developer
Advocate
On Tue, Mar 1, 2011 at 10:36 AM, Kurt Thomas kurt.a.tho...@gmail.comwrote:
When using users/lookup with 100 random
I just started getting this error message within the past hour for my
application. My application is read-only in the sense that it never
updates a user profile or posts any tweets or anything. My application
does, however, use the users/lookup.json API, and I use POST because I
am requesting many
Yes, we have a global catch-all rule that all POST operations are
write operations.
User/lookup is typically a GET operation anyway (
http://dev.twitter.com/doc/get/users/lookup ) and you can pass the
up-to 100 ids as a long query string parameter, provided your HTTP
implementation allows for the
I might be overlooking something, but it seems like users/lookup isn't
working. I tried it using my app credentials and got the following
message:
{
errors: [
{
code: 17,
message: No user matches for specified terms
}
]
}
Just to be sure, I went to
users/lookup seems not be working in the API console.
For instance: I signed in, and selected my application in the console
Headers and methods: GET / 1 / users/lookup
Parameters and values: user_id / 0
Response body: ... No user matches for specified terms ...
The same for parameters and
From search, and now looking at the page I apparently missed this big
warning:
Warning: The user ids in the Search API are different from those in the
REST API (about the two APIs /API-Overview). This defect is being
tracked by Issue
No problem. It's something high on our priority list to get rectified.
---Mark
http://twitter.com/mccv
On Fri, Apr 23, 2010 at 8:17 PM, Christopher Stumm christop...@stumm.ca wrote:
From search, and now looking at the page I apparently missed this big
warning:
Warning: The user ids in
Hi, I am using oauth and EPItwitter and I cannot get a decent response
from users/lookup. I keep on getting 401 Unauthorized when with the
same instance I can get any other method to work fine.
I tried navigating in the browser to
Hi Ninjamonk,
Slight error in the docs that I'll get fixed right now -- try this instead:
http://api.twitter.com/1/users/lookup.json?screen_name=dougw,raffi
Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod
On Thu, Apr 22, 2010 at 1:33 PM, Ninjamonk
I'm doing a call on users lookup and for some reason it's saying IDs
do not exist (for IDs I'd gotten from tweets that I got by doing a
search). For example when looking up the user elliottng (who from a
quick glance doesn't look like spam). The call I'm making is:
The userid for elliottng appears to be 4696. How did you get the 8467 value?
---Mark
http://twitter.com/mccv
On Thu, Apr 22, 2010 at 9:52 PM, stumm christop...@stumm.ca wrote:
I'm doing a call on users lookup and for some reason it's saying IDs
do not exist (for IDs I'd gotten from
I'm having a heck of a time getting the users/lookup to work. I keep
getting an invalid signature response, however if I try hitting
other urls that require authentication (such as statuses/
home_timeline) I get the proper response.
The only difference that I can see is that the users/lookup
creating oauth signatures is annoyingly subtle, isn't it? i would suggest
playing with
http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/
http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/and
verifying the signature base string and
That's the link I was looking for. Will play around and figure some of this
stuff out. Thanks Raffi!
- ryan.
On Mon, Apr 12, 2010 at 10:14 AM, Raffi Krikorian ra...@twitter.com wrote:
creating oauth signatures is annoyingly subtle, isn't it? i would suggest
playing with
23 matches
Mail list logo
