Use setlist.fm API rather than parsing raw HTML?

I was digging around and found setlist.fm have an API - https://api.setlist.fm/docs/1.0/index.html

@mattmooree thoughts on refactoring to use this instead of bs4 for parsing the HTML?

My initial reaction for using it is "no" because it's another login/auth set to manage. I don't want users having to sign up for setlist.fm for example. (I don't even have a setlist.fm account and I've been using it for years!) Also seems overkill for our current usage, perhaps there's potential for other features by leveraging it though.

Read the linked setlist.fm API documentation and inspect the existing BeautifulSoup HTML-parsing path. Compare the API's authentication requirements with the current user experience; the issue needs a decided integration direction and acceptance criteria before implementation can be considered done.

Written by the indexing model from the issue text.