You've got the request_token, next you'll need the access_token. With that, you'll do verify_credentials. Then Bob's your uncle..
On Aug 20, 10:37 am, "d.dinchev" <[email protected]> wrote: > Hello guys! > > I absolutely can not believe I haven't seen this in any tutorial, but > follow this scenario: > > I have user database with user IDs. The user has identified himself on > my application and he wants to allow it to use his Twitter account. I > get an authorization URL, the user follows the URL and allows my > application. Then he is redirected to the callback URL. OK, but in the > callback url I get his request token and don't know how to understand > which user actually allowed me to use his Twitter account so I can > store his access token! > > I have one idea to send the user id in the callback url eg: > example.com/?userid=1 > > Is there other solution to this one? > > Thank you so much for your support!
