Hi James, It sounds like you have the correct information for your application. As you are using your own personal access token and secret you don't need to be doing any of the OAuth authorization steps, but you do need to sign any request you make.
Are you using any PHP libraries to help you with this? There are a couple listed on http://dev.twitter.com/pages/oauth_libraries#php. Whether you are or not, can you share your signature base string and authorization headers (with the secrets and tokens removed) and we'll take a look. Thanks, Matt On Wed, Jun 30, 2010 at 8:54 PM, James Ford <[email protected]>wrote: > Thanks for the response. > > I am using the consumer key and secret found here: > http://dev.twitter.com/apps/<my > app id number> > > And the access token and secret found here: http://dev.twitter.com/apps/ > <my > app id number>/my_token > > No joy. > > On Jun 30, 9:47 pm, "Andrew W. Donoho" <[email protected]> > wrote: > > On Jun 30, 2010, at 14:32 , James Ford wrote: > > > > > One thing I'm perhaps not clear on, do I need xAuth for this to work? > > > > You do need to get the access token somehow. That is what xAuth provides > you. That said, you sound like you are a server app. Twitter doesn't support > xAuth for server apps. You probably need to use the standardOAuthtoken > request protocol. > > > > Anon, > > Andrew > > ____________________________________ > > Andrew W. Donoho > > Donoho Design Group, L.L.C. > > [email protected], +1 (512) 750-7596 > > > > "To take no detours from the high road of reason and social > responsibility." > > -- Marcus Aurelius > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
