Guides

Free Bible APIs compared (and when you don't need one)

3 min read · last updated 2026-11-18

Do you actually need a Bible API?

It’s worth asking, because a lot of the time you don’t. If you only need public domain translations, you can download the whole text once and ship it with your app. It’s about 4 to 5 MB of plain text for an English Bible. No network requests, no rate limits, works offline. The Berean Standard Bible and eBible.org both have downloads ready to go.

An API makes sense when you want lots of translations without storing them, when you need copyrighted text that you can only get through an approved API, or when you’re building a quick prototype and don’t want to parse files yet.

Here are the free options I’d look at first.

bible-api.com

The simplest one. Made by Tim Morgan, open source, and you don’t need a key.

GET https://bible-api.com/john+3:16
GET https://bible-api.com/john+3:16?translation=kjv
GET https://bible-api.com/romans+8:28-39?translation=bsb

You get back JSON with the reference, the full text, and an array of individual verses. It supports a few dozen public domain translations, including the WEB (the default), KJV, BSB, ASV, Darby and the Douay-Rheims, plus some non-English ones.

The limit is 15 requests every 30 seconds per IP address. It’s free as long as you don’t abuse it, and there’s no guarantee it’ll always be up. That’s fine for side projects and learning. For anything serious, either cache your results or run your own copy, since the code is MIT licensed.

HelloAO Free Use Bible API

bible.helloao.org takes a different approach. Instead of a server that answers queries, it’s a big set of static JSON files. At the time I’m writing this it lists over 1,500 translations in over 1,100 languages. No key, and no usage limits listed.

GET https://bible.helloao.org/api/available_translations.json
GET https://bible.helloao.org/api/BSB/books.json
GET https://bible.helloao.org/api/BSB/JHN/3.json

Books use the standard three-letter codes like GEN, JHN and 1CO (see the file formats guide for more on those). A chapter comes back with its verses, footnotes, and links to the previous and next chapters.

One thing to know: each verse’s content is an array of pieces, not a plain string, so you’ll want a small helper function that turns it into text. Also keep in mind that each translation still has its own license. The API is free, but that doesn’t make every translation in it public domain. Check the license info for the one you use.

API.Bible

API.Bible is run by the American Bible Society. You need to sign up for a key, and you send it in an api-key header with each request.

The free plan gives you 5,000 calls a month, all the public domain and openly licensed Bibles, and up to three copyrighted Bibles for non-commercial use. The paid plans give you more calls, and commercial apps pay a license fee for each copyrighted translation.

There’s also something called FUMS (Fair Use Management System). It’s basically usage reporting for the publishers. Web apps are required to include it, either with a small JavaScript snippet or by calling their endpoint with a token that comes back in each response. Mobile-only apps can skip it.

5,000 calls a month is not a lot if you request one verse at a time. Fetch whole chapters and cache them.

ESV API

If you specifically need the ESV, use Crossway’s API. It’s free for non-commercial use, which they define as nothing charged for access and no ads or sponsorships.

The limits are 5,000 requests a day, 1,000 an hour and 60 a minute. You can’t get, show or store more than 500 verses or half a book (whichever is less) at a time. You have to show the ESV copyright notice and link to esv.org on any page that uses the text. And Crossway does not allow ESV text to be processed by AI systems. More on that in the licensing guide.

Which one should you use?

If you’re just learning or making something small, start with bible-api.com. It’s the quickest to get working.

If you need lots of languages or want to avoid rate limits, use HelloAO, or download the JSON and serve it yourself.

If you need copyrighted translations, it’s API.Bible or the publisher’s own API.

And if you only need one or two public domain translations, honestly, just download them. It’s simpler, faster for your users, and one less thing that can break.

Be a good neighbor

All of these are run by small teams or ministries, and some by one person in their spare time. Cache what you fetch. Don’t hammer them in a loop while you’re debugging. If a project helps you, star it, report bugs, or send a thank-you. That stuff matters more than you’d think.


Questions or corrections? Ask in the forum.

Other guides