Hello,

you are right!
I put the "api" in the front and I changed the authenticate to authorize and
it worked!

thanks - I will refer your twitter username to our app fans!

On 12 July 2011 17:11, Taylor Singletary <taylorsinglet...@twitter.com>wrote:

> On the step where you arrive at Twitter's credential screen, what URL do
> you see in the browser bar?
>
> If it's the URL that's being returned by your authenticateURL function,
> then it's a URL that can't upgrade your tokens. You want to use the URL
> returned in the autorizeURL function instead.
>
> Also, these URLs are out-of-date. They should have the "api" subdomain
> attached, like https://api.twitter.com/oauth/access_token
>
> @episod <http://twitter.com/intent/user?screen_name=episod> - Taylor
> Singletary
>
>
> On Tue, Jul 12, 2011 at 9:05 AM, Nencho Lupanov 
> <nlupa...@googlemail.com>wrote:
>
>> Hi again,
>>
>> here is what i have set in my Oauth library:
>>
>>   function accessTokenURL() { return '
>> https://twitter.com/oauth/access_token'; }
>>   function authenticateURL() { return '
>> https://twitter.com/oauth/authenticate'; }
>>   function authorizeURL() { return 'https://twitter.com/oauth/authorize';
>> }
>>   function requestTokenURL() { return '
>> https://twitter.com/oauth/request_token'; }
>>
>> Please advice if it needs to be changed?
>>
>> On 12 July 2011 16:13, Taylor Singletary <taylorsinglet...@twitter.com>wrote:
>>
>>> Hi everyone on the thread,
>>>
>>> When you're having this problem, what endpoints are you using for
>>> authentication?
>>>
>>> Make sure that you're using https://api.twitter.com/oauth/authorize on
>>> the "redirect to Twitter" step of OAuth. If you're using
>>> https://api.twitter.com/oauth/authenticate, you'll never be able to
>>> negotiate a higher than RW access level token, regardless of what you've
>>> configured in your application detail settings.
>>>
>>> @episod <http://twitter.com/intent/user?screen_name=episod> - Taylor
>>> Singletary
>>>
>>>
>>>
>>> On Tue, Jul 12, 2011 at 7:54 AM, twittme_mobi 
>>> <nlupa...@googlemail.com>wrote:
>>>
>>>> The same problem here - i am not sure if the api guys are aware of the
>>>> consequences every change they make...
>>>>
>>>> On Jul 12, 1:33 am, Mr Blog <mrblogdot...@gmail.com> wrote:
>>>> > I have the same problem.
>>>> >
>>>> > On the App settings it is set to:
>>>> >
>>>> > "Read, Write and Accessdirectmessages"
>>>> >
>>>> > But when users authenticate with OAuth, it's telling users:
>>>> >
>>>> > This application will not be able to:
>>>> > Access yourdirectmessages.
>>>> >
>>>> > How do we fix this?
>>>> >
>>>> > On Jul 4, 5:38 pm, "alexre...@gmail.com" <alexre...@gmail.com> wrote:
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > > Most of my apps require read access forDirectMessages, but they're
>>>> > > only reading from one account.  Many users DM to one account and I
>>>> > > need access to that one account to grab all the DMs (which no longer
>>>> > > works as of June 30th).
>>>> >
>>>> > > I changed the Access Level of all my apps to Read, Write andDirect
>>>> > > Message, but it doesn't seem that the change has taken place, or I'm
>>>> > > missing something, somewhere in terms of what I need to do?
>>>> >
>>>> > > When I try and re-authorize an account I see the following on the
>>>> > > Twitter / Authorize screen:
>>>> >
>>>> > > This application will not be able to:
>>>> > > Access yourdirectmessages.
>>>> > > See your Twitter password.
>>>> >
>>>> > > What else do I need to do?  I have confirmed that the application
>>>> > > settings on Twitter do say, Read, Write andDirectMessagesfor my app
>>>> > > but I can only use "my access token" (for the Twitter handle
>>>> > > associated with the app) to accessdirectmessages, anytime I try and
>>>> > > re-authorize any account through my actual app, I see:
>>>> >
>>>> > > This application will not be able to:
>>>> > > Access yourdirectmessages.
>>>> > > See your Twitter password.
>>>> >
>>>> > > ... which isn't inline with how I setup the settings.  Any help
>>>> would
>>>> > > be greatly appreciated.  I'm really hoping I'm missing something
>>>> small
>>>> > > here.
>>>>
>>>> --
>>>> Twitter developer documentation and resources:
>>>> https://dev.twitter.com/doc
>>>> API updates via Twitter: https://twitter.com/twitterapi
>>>> Issues/Enhancements Tracker:
>>>> https://code.google.com/p/twitter-api/issues/list
>>>> Change your membership to this group:
>>>> https://groups.google.com/forum/#!forum/twitter-development-talk
>>>>
>>>
>>>  --
>>> Twitter developer documentation and resources:
>>> https://dev.twitter.com/doc
>>> API updates via Twitter: https://twitter.com/twitterapi
>>> Issues/Enhancements Tracker:
>>> https://code.google.com/p/twitter-api/issues/list
>>> Change your membership to this group:
>>> https://groups.google.com/forum/#!forum/twitter-development-talk
>>>
>>
>>  --
>> Twitter developer documentation and resources:
>> https://dev.twitter.com/doc
>> API updates via Twitter: https://twitter.com/twitterapi
>> Issues/Enhancements Tracker:
>> https://code.google.com/p/twitter-api/issues/list
>> Change your membership to this group:
>> https://groups.google.com/forum/#!forum/twitter-development-talk
>>
>
>  --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> https://groups.google.com/forum/#!forum/twitter-development-talk
>

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Reply via email to