I just want to check if a username exists in Twitter. I thought it would be part of the API, but cannot find it on the api wiki http://apiwiki.twitter.com/w/page/22554679/Twitter-API-Documentation.
Any ideas?
thanks
JP
It seems that I can pass screenname in the user search API. And I have to check for 404 not found status (if username does not exist). Seems a bit ugly, but might just work. Better suggestions welcome!
this gives 404:
http://api.twitter.com/1/users/show.xml?screen_name=thisdoesnotexist1234abxfd
this returns valid info:
http://api.twitter.com/1/users/show.xml?screen_name=billgates
thanks
JP
EDIT
The Twitter REST API v1 is no longer active. Please migrate to API
v1.1. https://dev.twitter.com/docs/api/1.1/overview.
#JP Even if the twitter api rate limit has been reached , 404 would be returned. SO this is as you said a dirty method. take into consideration the rate limit and add sufficient checks in your code so as not to reach them. the above method should work fine.
regards,
Related
I find this on official doc for client ID :
During your initial setup you will need to contact Valve with the following information:
What permissions you need the user to obtain. The required permissions are listed below with each API call.
The token lifetime.
The redirect URI to send the user back to after completing authentication/authorization.
In return, Valve will assign a Client ID for your implementation.
But they didn't mention how to contact valve for the same. I found many same questions on different platform but can't find any solution to this.
https://steamcommunity.com/oauth/login?response_type=token&client_id=client_id_here&state=whatever_you_want
I am little confuse in steam-ID and Client-ID. Are they the same? if not then how to retrive client-id from valve.
Sorry If i miss anything here
Answering my own question for someone's reference.
O-auth is not supported in stream any more, But official documentation is still there which is useless right now.
Need to implement it using Open-ID which is the only solution.
There are many PHP and other language's reference on git-hub.
If anyone need any help feel free to ask here i have implemented it successfully.
And also client-id and steam-Id are not same.
I would like to change twitter pfp via requests but NOT BY API
there is one parametr that describe whole image to upload:
and I dont understand where it takes place, maybe someone have already tried to do this and figured out?
Thank you in advance
The media_id parameter is returned from the media upload API endpoint. You will need to use the Twitter API to accomplish this.
I want to get list of endpoints in Kaa, I see many REST functions here but all of them need informations like Endpoint Hash Key and ... but I don't know how I can find them. Anybody can help me how I can do this ? and is there a way for geting event on device discovery in Kaa ?
Thanks in advance
On your link for each Rest call, there is the description with the endpoint cresponding to the request. For example:
Get user authentication status
URL : /kaaAdmin/rest/api/auth/checkAuth
Same for parameter needed.
If that's not what you are looking for, you might have to explain a little bit more.
You are able to get endpoint key hash in 3 ways :
Get information from Client SDK on your device. Check appropriate documentation of you desirable SDK.
Look at Admin UI in Endpoint profiles menu.
Get via Admin REST API .
Please, check profiling section.
I think it will help you to find your desired information.
I am new in Twitter API. I have a requirement like I have to pull the information of an authenticated twitter user to know the number of followers. I can do this using REST API but I have a problem here. So I have taken the way to use Twitter User Streams.
I am not able to integrate this functionality in the site. I am using twitter console( https://dev.twitter.com/console ). But there I am not able to get any kind of result, it actually hangs/shows gateway timeout. And that's for I am not able to configure that how to write the code for this or how to use this in site. I am not passing any kind of parameters.
So, any body can please help in this would be very grateful( a clean sample code for this or any link where to get the good documentation ). I have already checked with twitter dev documentations.
Thanks in advance :)
My Problem might be simple, but i just dont know how the pageViewer/pageOwner concept work or its better to say i dont know how i can get rid of this system.
I just want to make a Gadget, which handles all Oauth-authentifications for Networks like Twitter, Google+ etc.
So basicly i want to let the User say how many Networks he wants to access and then i make all Oauth-authentifications, i use Liferay and Opensocial for that task but get this error:
OAuth error: UNKNOWN_PROBLEM: Client state belongs to a different person (state owner=G-10180, pageViewer=10196) ==== Original request: GET /m8/feeds/contacts/default/base?alt=json Host: www.google.com X-Shindig-AuthType: oauth X-Forwarded-For: 87.139.78.177 X-shindig-dos: on ====
I guess i have to change something in the shindig.properties file, but this is where i need your help.
-------------------------------UPDATE----------------------------------
I know that the first part of my Authentication works because i get a authentication token, but it is invalid. I assume that the gadget expects a token identical to the token the owner stored.
It would be perfect if you have a little code example for me to identify the viewer as new user if he isnt already a member. Please tell me where i have to put this code in my gadget because the documentation of opensocial costed much lifetime til now, but i cant find an answere to this issue :).
Thanks in advance
Please see my response to your other question: link
You're basically encountering the same problem where the viewer is not the page owner. As I mentioned in your other question, the page viewer must be the page owner for OAuth gadgets (in other words, you must add the OAuth gadget to a page you own).
I'm hoping that a future version of Shindig will fully support adding OAuth gadgets to pages where the viewer != owner, but I'm having difficulty getting feedback from the Shindig community (see here)