Switch to using API in addition to Scraper Approach #6
Description
Redesign a hierarchical structure for fetching Bible translations, which first attempts to use an online Bible API, and then, only if the content is unavailable, reverting to using the current Bible.com scraper (since YouVersion doesn't publish an API). Even though the scraper, when used correctly, is not in breach of copyright (and provides access to more translations than any API I could find), it is much cleaner to use an API. Essentially, a Fetcher class will need defined with subclasses for each API source (and one for the scraper).
Potential APIs to include:
- https://docs.api.bible/ (1500+ versions, but NIV, ESV etc only seem to be availble on request)
- https://bible.helloao.org/docs/guide/making-requests.html (1000+ versions, but NIV, ESV etc not available)
- https://www.biblegateway.com/api/documentation (smaller number of translations, but has all the most popular English versions)