Hi, I am currently creating an application for a school project and it will not be hosted as a legit website. What should I fill into the Website URL, Callback URLs, Terms of Service URL and Privacy policy URL respectively? My project will only be ran on a localhost page. I have attached a screenshot for easy reference. Thank you!!!
Just my opinion, so don’t rely on this too much but - Privacy policy / TOS links don’t really apply unless you’re going to be involving other users - in that case you should maybe consider getting a standard one. Either way, Do describe this in the “Tell us how this app will be used” part.
Callback URL is only used if you intend to use that functionality somehow. Don’t tick “Enable Sign in with Twitter” if your app isn’t going to need other users to sign in (like if it’s a localhost demo) - you’ll generate your own “sign in” in the dev settings / App details anyway.
For website you can use your github repo maybe? Or better still, use something like https://ngrok.com/ to set up a URL to your localhost server (same for Callback URL)
2 Likes
As a Twitter staff member I’d agree with everything that @IgorBrigadir describes here.
The absolute most important aspect of the form is the “use case” and why you want to use the API and how you’ll use the results.
If your app is not a web app and particularly if you’re not implementing Sign in with Twitter then most of the URL fields are not relevant.
Thanks for applying to use the API!
1 Like
