Hey Steve,

To expand on Tom's message, Basic Auth is no longer supported on the
Twitter API and you need to update your script to use OAuth. In
addition you want to make sure the URL you are calling is pointing to
http://api.twitter.com/1/statuses/update.xml - all API requests should
go through http://api.twitter.com now.

Information about transitioning from basic to OAuth is here:
    http://dev.twitter.com/pages/basic_to_oauth

There are community libraries available which may be of help:
    http://dev.twitter.com/pages/oauth_libraries

Hope that explains why your script stopped working and what you can do
to get it working again.
Matt



On Fri, Sep 3, 2010 at 9:42 AM, Tom van der Woerdt <i...@tvdw.eu> wrote:
> http://dev.twitter.com/announcements
>
> Tom
>
>
> On 9/3/10 6:35 PM, MrMoxy wrote:
>> Raffi,
>>
>> I have been using the API to tweet twice daily for months, but my
>> script suddenly stopped working yesterday morning. I am posting to
>> this page using a curl connection
>>
>> http://twitter.com/statuses/update.xml
>>
>> and it keeps returning a 401 error. I have verified that my username &
>> password have not changed. Does the error have something to do with
>> the changes you made? How can I fix this?
>>
>> Thanks!
>>
>> Steve
>> SEJohnsen at gmail.com
>>
>>       $mypost=$data['post'];
>>       $twitter_user = "user";
>>       $twitter_password = "pwd";
>>       $twitter_api_url = "http://twitter.com/statuses/update.xml";;
>>       $twitter_data = "status=".$mypost;
>>
>>       $ch = curl_init($twitter_api_url);
>>       curl_setopt($ch, CURLOPT_POST, 1);
>>       curl_setopt($ch, CURLOPT_POSTFIELDS, $twitter_data);
>>       curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1);
>>       curl_setopt($ch, CURLOPT_HEADER, 0);
>>       curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
>>       curl_setopt($ch, CURLOPT_USERPWD, "{$twitter_user}:
>> {$twitter_password}");
>>
>>       $twitter_data = curl_exec($ch);
>>       $httpcode = curl_getinfo($ch, CURLINFO_HTTP_CODE);
>>       curl_close($ch);
>>
>>
>> On Aug 27, 7:03 am, Raffi Krikorian <ra...@twitter.com> wrote:
>>> hi all.
>>>
>>> this is most certainly a mistake on our part - we'll be reverting this
>>> change.
>>>
>>> On Fri, Aug 27, 2010 at 4:45 AM, Cameron Kaiser <spec...@floodgap.com>wrote:
>>>
>>>>> It looks like error responses have changed, at least for users/show.
>>>
>>>>> I used to get:
>>>>> {"error":"User has been suspended"}
>>>
>>>>> Now, I get:
>>>>> {"errors":[{"code":63,"message":"User has been suspended"}]}
>>>
>>>> I'm seeing that too. When did this change?
>>>
>>>> --
>>>> ------------------------------------ personal:
>>>> http://www.cameronkaiser.com/--
>>>>  Cameron Kaiser * Floodgap Systems *www.floodgap.com*
>>>> ckai...@floodgap.com
>>>> -- They told me I was gullible ... and I believed them.
>>>> -----------------------
>>>
>>>> --
>>>> Twitter developer documentation and resources:http://dev.twitter.com/doc
>>>> API updates via Twitter:http://twitter.com/twitterapi
>>>> Issues/Enhancements Tracker:
>>>> http://code.google.com/p/twitter-api/issues/list
>>>> Change your membership to this group:
>>>> http://groups.google.com/group/twitter-development-talk?hl=en
>>>
>>> --
>>> Raffi Krikorian
>>> Twitter Platform Teamhttp://twitter.com/raffi
>>
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk?hl=en
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Reply via email to