"Non-public" app


#1

Do all apps developed through the API have to be publicly accessible?

I’m developing a facility to check the latest tweet of a certain user, to be embedded on an internal, non-public, service. I used to deal with it via endopints like https://twitter.com/statuses/user_timeline/.json

Will this still be possible using the new authenticated API? Or am I forced to provide this publicly, if I want the service to run?


#2

No requirement that apps be public. You’ll want to make sure you use valid endpoints though – https://api.twitter.com/1/statuses/user_timeline.json is the correct endpoint for a user timeline, and you need to specify a screen name or user ID.

Authorization doesn’t require you to provide anything publicly.