Table of Contents
API.Bible allows any developer to include Scripture content and text anywhere in their website or application for non-commercial purposes. If you're not a developer, and want to include Scripture content or API.Bible on your website, check out some of our utilities here. For you developers, API.Bible is a REST-based API and you can read the complete documentation here.
To access the API, you must be a registered API.Bible user and have activated your unique API token by signing up here. Once you have your API token, you can make calls to the API and retrieve content. Please remember that every call you make must include this API token. Your API token is unique to you. It's a secret, so don't share it with anyone else!
You cannot use the Scripture content retrieved from the API for any commercial purposes, nor in any application that is illegal, offensive, obscene, violent, immoral, or derogatory towards other or the Scriptures itself. Basically, play nice. Don't alter or change the meaning of the Scripture, or how it could be interpreted. If you do want to use this content for commercial purposes, you must get specific approval by contacting us via email at firstname.lastname@example.org with API in the subject header. Further, we ask that you only display 500 email@example.com consecutive verses at a time, and always include the copyright information for the versions you are using along with the Scripture content you display. You can also review our complete API Terms and Conditions here.
As long as your are using the Scripture content in a non-commercial, positive manner that respects the integrity of the Scripture text as described above, you can create whatever you want. We are always curious what developers can dream up, so please share your creations with us and the community in the API.Bible forum.
Currently, for non-commercial applications, we are able to offer all public domain texts listed under the 'Bibles' section, the Contemporary English Version (CEV), Good News Translation (GNT), and the King James Versions (KJVA). We want to make as many versions available to you as possible, but we have to get all the various publishers on board first. If there is something you really want to have access to, let us know either via email or on our forums and we will do everything in our power to work with you!
Scripture versions are intellectual property of various publishers and license owners. To give access to the version via the API, we have to get special permission from the various publishers first. If there is something you want, the fastest way to get that permission is to speak up and request access to versions on our API.Bible Forum. If you let us know what you want, we can approach the publishers and try our best to make it happen. To help build trust with the publishers and intellectual property owners, we've built the Fair Use Management System into the API. This helps us provide an extra layer of data on how Scripture content is being consumed by API users and ultimately your application's end users. We are really trying to emphasize transparency with how Scripture content is used via our API, as that will show publishers and IP owners that we are protecting their content and ensuring it maintains the integrity Scripture deserves.
The Fair Use Management System will help us to provide information to Scripture publishers that shows them how their content is being used. It will help us to add more Scripture versions to the API as we demonstrate the additional reach that API access gives to a version. And it will help us to allocate our development and physical resources to ensure that the API expands to include features and data that are important to API users.
You can cache data, but we request that you limit it to fewer than 500 consecutive verses. We also recommend that you clear your cache every 14 days or less because we are constantly updating the structure of our data and improving it to make it more accessible for you. With that in mind, it's not a great idea to cache things for a long time because we want you to have the most up to date Scripture content available.
Yes, there is a default rate limit. You may only perform 5,000 queries a day. If you are building a massive application that will require more queries than this per day, please contact us via email or on the forum so we can work something out that will accommodate your needs! Ultimately, we want to provide you with access to the Scripture content you need while protecting our servers at the same time.
We are definitely open to it! Drop us a line at firstname.lastname@example.org with API in the subject header and let us know what you are working on and what type of access you need. We are ](email@example.com)more than happy to work with you and try to meet your needs.
To get started with the API, we suggest you read over the complete documentation to see the capabilities and limitations of the current API. If you are lost or stuck, check out our API.Bible Forum to ask the community for help. We also read the forum daily and will respond to questions or troubleshooting issues. If you want immediate help, submit a ticket request from the forum and we will get back to you as soon as possible.
Yes. We firmly believe it's important to give credit to the publishers who own the rights to the particular version of Scripture content. As such, please include the copyright information along side all of the Scripture you display.
If you are a publisher or intellectual property owner and want your Bible version to be made available via API.Bible, we'd absolutely love to hear from you. Drop us a line at firstname.lastname@example.org.
We have a forum for you to explore community questions and contributions, as well as articles from our development team. If you can't find what you're looking for there and want immediate help, drop us a line at email@example.com.