Checking whether a user has given permission to Private Messages

[Tyson Lowery]

Is there a way to check whether a user has explicitly granted
permission to their Private Messages?

[James Estes]

I don't think so, but looks like its coming soon. 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

James

On Mon, May 23, 2011 at 4:20 PM, Tyson Lowery <tyson...@gmail.com> wrote:
> Is there a way to check whether a user has explicitly granted
> permission to their Private Messages?
>

> --
> 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
>

[Tyson Lowery]

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.

[Arnaud Meunier]

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-faq will be udpated in a minute :)

Hope that helps,

Arnaud / @rno

[Arnaud Meunier]

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

[Stephen Rife]

> The FAQ onhttp://dev.twitter.com/pages/application-permission-model-faqwill

> be udpated in a minute :)
>

Here's the URL
http://dev.twitter.com/pages/application-permission-model-faq

[Yusuke Yamamoto]

Hi,

The doc says, “read-write-directmessages” (Read, Write, & Direct Message)

But actually I get "read-write-privatemessages" as you mentioned.
It's a doc bug, right?

Best,
--
Yusuke Yamamoto
yus...@mac.com

this email is: [x] bloggable/tweetable [ ] private
follow me on : http://twitter.com/yusukeyamamoto
subscribe me at : http://samuraism.jp/

[Matt Harris]

Hi Yusuke,

We are standardizing the phrasing to match the API requests so in this case the docs are correct.

We have a fix to correct messages to 'direct' instead of 'private' on it's way.

@themattharris