I last researched this a few years ago, but the best resource I’ve found in this space is: https://getbible.net/api https://getbible.net/api They’ve taken a di

I last researched this a few years ago, but the best resource I’ve found in this space is: https://getbible.net/api https://getbible.net/api They’ve taken a different approach to retrieving content - instead of a navigable resource hierarchy you send a citation that approximates the standard format: https://en.wikipedia.org/wiki/Bible_citation https://en.wikipedia.org/wiki/Bible_citation This matches one of the most common use cases for a Bible API: turning a citation into content. It’s also worth scanning your content to find if there are characters that will break JSON serialization. For example, many translations distinguish supplied words by special characters: I’ve seen square and angle brackets used. It’s not an easy domain to represent once you start handling special cases, but very worthwhile.