Hi Tamara, Just use placeholder data on dev.twitter.com/apps while registering your application. You can use your @username as the name for your application or something similar. For the callback URL -- this value is really just a placeholder for all intents and purposes anyway, and so as long as you can provide a valid URL there, you should be fine. With OAuth, you must specify your callback URL explicitly on the request token step anyway.
After creating your application record, you can then use your API key and secret to negotiate OAuth tokens and make calls from there. API methods that don't require authentication also don't require that you use an API key to access the resource, instead you could just simply explore the API using curl or a simple HTTP library and move on from there. Many beginners with OAuth find the tips on this page useful as well: http://dev.twitter.com/pages/oauth_single_token @episod <http://twitter.com/intent/user?screen_name=episod> - Taylor Singletary On Wed, Jun 15, 2011 at 9:58 AM, t.williams <tamara.mr.willi...@gmail.com>wrote: > Hello Developers: > > I have always heard of Twitter but just recently created a Twitter > account. I want to develop an app which will use the Twitter API and > more specifically the REST API to collect public Tweets and then > perform some processing. I have been reading the documentation but > still have a long way to go. Therefore, my concern is that my > application is still in the design phase of the software lifecyle > which means that I have not yet decided on a name and there is no > website or callback URL. How then would I be able to perform a > registration? I wanted the flexibility to code in functions or classes > and test by making calls to the API instead of waiting until the full > application was complete. However, in order to get developer access to > the Twitter API I need to register the app and also according to the > Authentication pages, registration is needed in order to use OAuth. I > also looked at Twitter4J which also requires the use of OAuth. I am > grateful for any advise that you can give. Thank you. > > Cheers, > T Williams > > -- > 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
