API Registration vs User Login


#1

I have some python scripts that are already working on an existing site, checking Twitter for tweets that match certain criteria. I want to set them up on a new server and I need to use a different account. I’m unable to speak to the person that set them up initially because of health issues.

I can see an entry for USER and PASS in a config file as well as STREAM_URL = “https://stream.twitter.com/1/statuses/filter.json

Can someone tell me if I just use my Twitter User account credentials or if I need to register for the API?

The scripts are very simple. They do not handle anything other than searches, so no user credentials are authorised. I’m wondering whether the API is needed or not. My knowledge of python and the twitter api is limited but I’m fairly knowledgeable about php/mysql and so if I can tweak the config and localise the scripts I’m sure they will be plug and play… can someone point me in the right direction so I can get their functionality back online. Thank you.


#2

Hi @quotesuk,

The Streaming API still supports “basic auth” – a username and password – for logins. It won’t support this method of authorization forever but we’ve also not yet announced any kind of date for that support to end. Your own username and password should work fine with that method.

You may want to revise your API URL, as the v1 Streaming API is deprecated and will no longer function after March 2013. Try https://stream.twitter.com/1.1/statuses/filter.json instead – you’ll find little to no differences in the response format.


#3

Thank you - I’ll give this a go.

I will also see if the scripts can be adapted to use the new URL you’ve suggested.