Custom twitter app all of sudden stopped updating status and I'm new to Twitter.
<errors>
<error code="34">Sorry, that page does not exist</error>
</errors>
Stack Trace:
at TwitterOAuth.WebResponseGet(HttpWebRequest webRequest)
Custom app is using the following resource url:
"https://twitter.com/statuses/update.xml"
Found a Code Project example that uses the following resource url and it worked for me:
"http://api.twitter.com/1/statuses/update.json"
http://www.codeproject.com/Articles/247336/Twitter-OAuth-authentication-using-Net
So I tried
"https://api.twitter.com/1/statuses/update.xml"
Got the following error:
Unhandled Exception: System.Net.WebException: The remote server returned an erro
r: (403) Forbidden.
at System.Net.HttpWebRequest.GetResponse()
now, twitter published new API V1.1
and the old API v1.0 will be retired on March 5th, 2013.
so you should review API V1.1
Related
I was previously using the following code to retrieve data about Eventbrite events:
file_get_contents('https://www.eventbriteapi.com/v3/users/me/events?status=live&token=xxxxxx');
This was working just fine a few months ago. However when I've tried it again, I now get a "failed to open stream: HTTP request failed! HTTP/1.1 404 NOT FOUND" error. I've checked the Eventbrite API documentation https://www.eventbrite.com/platform/docs/events and it seems that the URL structure is still correct.
This user and token definitely exists, as I can run the following code which does give valid results:
file_get_contents('https://www.eventbriteapi.com/v3/users/me/organizations?token=xxxxx')
What is wrong with my Events code?
I am trying to log into my SoundCloud account on an iOS app I develop using the Objective-C SoundCloudAPI framework https://github.com/sangtn/SoundCloudAPI
This worked like a charm the last time I used it but by today I am getting the following error message:
Error Domain=NXOAuth2HTTPErrorDomain Code=401 "HTTP Error: 401"
UserInfo={NSLocalizedDescription=HTTP Error: 401}
Using the same credentials (email and psw) grants me access on the web platform and on the SoundCloud iOS app.
I cannot find any recent changes on the SoundCloud platform nor does their status page indicate any malfunction, so I am asking if anyone is experiencing this as well and if someone has found a cause of this issue?!
Thanks!
Looks soundcloud fixed the issue
Having issues as of last night with my app logging in as well. I've Tweeted and emailed - seems like this could be a broader issue on their side.
I am getting 1001 error code while integrating cc-avenue using Asp.Net MVC.
It also showing that Encrypted request is invalid/not present.
I am not able to trace this error in cc-avenue error code list.
please help me.
When i make the following request as mentioned in yahoo open id doc spec, i am getting error : Sorry! You will not be able to link your Yahoo account with this website or application. It is using an older version of the OpenID technology.
Request i am making is :
https://open.login.yahooapis.com/openid/op/auth? openid.claimed_id=http://specs.openid.net/auth/2.0/identifier_select &openid.identity=http://specs.openid.net/auth/2.0/identifier_select &openid.mode=checkid_setup &openid.ns=http://specs.openid.net/auth/2.0 &openid.realm=http://ec2-54-200-227-210.us-west-2.compute.amazonaws.com/ &openid.return_to=http://ec2-54-200-227-210.us-west-2.compute.amazonaws.com/ &openid.ns.oauth=http://specs.openid.net/extensions/oauth/1.0 &openid.oauth.consumer=consumer_key
What could be the reason ?
I am getting an error `Domain=HTTP Code=410 "The operation couldn't be completed. (HTTP error 410.)". in iOS application development.
This code previously worked fine but now it is throwing an error.
You might be using v1.0 of the Twitter API.
Then, the solution is to switch to version 1.1.
See: https://dev.twitter.com/blog/api-v1-is-retired
Overview of 1.1 API:
https://dev.twitter.com/docs/api/1.1/overview
Seems that you are using V1.0 of the twitter API. Check Resource URL it might be https://api.twitter.com/1/ instead of https://api.twitter.com/1.1/
For further detail check https://dev.twitter.com/docs/api/1.1/overview