Hi Z-13,

Some recommendations first:

  * When performing the OAuth token negotiation operations, it's
recommended to use SSL and the hostname api.twitter.com.
https://api.twitter.com/oauth/access_token
  * It's much easier to debug OAuth when you use HTTP headers to
transmit the OAuth parameters rather than using them on the query
string.

Some specific areas that might be giving you trouble:
  * The access_token endpoint doesn't take an oauth_callback -- you
provide that value on the request_token step, we take note of it, and
present the PIN code flow after you've sent the user to our authorize
end point. You should not have an oauth_callback value on the access
token step.
  * Consider using a more robust oauth_nonce than a numerical sequence.

If you're still having problems, please post an example signature base
string you are generating for this step and we'll see if there's
something else going on.

Thanks,
Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod



On Mon, May 17, 2010 at 1:03 PM, Z-13 <y...@yandex.ru> wrote:
> Help me, please!
>

Reply via email to