Hey again,

For more consistency, the X-Access-Level header value for the "Read, Write &
Direct Message" scope is going to be "read-write-directmessages" (rather
than "read-write-privatemessages"). We'll also update the Client Application
management pages (using "Direct Messages" and not "Private Messages") to
match the API methods being called.

   Arnaud / @rno <http://twitter.com/rno>



On Mon, May 23, 2011 at 4:18 PM, Arnaud Meunier <arn...@twitter.com> wrote:

> We just started to return the "X-Access-Level" header for authenticated API
> requests, that tells you what access level the user token has:
>
> - "read" (Read-only)
> - "read-write" (Read & Write)
> - "read-write-privatemessages" (Read, Write, & Private Message)
>
> The FAQ on http://dev.twitter.com/pages/application-permission-model-faqwill 
> be udpated in a minute :)
>
> Hope that helps,
> Arnaud / @rno <http://twitter.com/rno>
>
>
>
> On Mon, May 23, 2011 at 3:26 PM, Tyson Lowery <tysonlow...@gmail.com>wrote:
>
>> I think I found the answer from themattharris:
>>
>> > How do we know what the access level of a user token is?
>>
>> This is a great idea and one the team has discussed. What we are
>> going
>> to do is add a new header to authentication requests that will tell
>> you the access level of the token you authenticated with. We’re
>> working on this now and hope to have it released in the next few
>> days.
>>
>> --
>> 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