Long-term is to provide list of venues to IFTTT triggers. Short-term is to process/sanitize strings from IFTTT

The app shouldn't tie DB updates to IFTTT calls. The data updates should be on a local schedule.

Add Oauth flow to get User Token (store in model)
Get User name using Endpoint: /v4/user/info/
Remove POST form entry from '/' template
Save access_token for user as session variable
Add response parsing routines to dashboard Displays wishlist beer for user and a few public checkins for that beer

Rate-Limiting
All API applications are rate-limited to protect against abuse and keep the platform healthly. The default limit for API access is 100 calls per hour per key. If you are using Authentication, the rate limit is applied to the user, instead of the API key.

Prototyping code should be removed.

Pull in url.py

Untappd provides a non-authentication RSS feed for venue checkins.

• find RSS parser
• extract relevant data and store in DB
• provide endpoint to access this data

Monitor City Beer Store website for changes to beer on tap menu and maintain a list.
When a beer is removed, remove it from the stored list and create an event.
When a beer is added, add it to the stored list and create an event.
When IFTTT hits API point, send events for all matching beer at a the venue for the input Brewery.

Twitterfy data to remove spaces on returned data.

__get_website_event_records
__get_update_records

Create utility class for:
json_builder
test results
etc.