Overview
Bible works by querying a large database of bible verses to retrieve the verse based on the book, chapter, and verse provided. It returns the bible verse in a structured format.
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl "https://api.apiverve.com/v1/bible?book=Genesis&version=KJV&chapter=5&verse=17" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/bible?book=Genesis&version=KJV&chapter=5&verse=17', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/bible?book=Genesis&version=KJV&chapter=5&verse=17",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/bible?book=Genesis&version=KJV&chapter=5&verse=17", nil)
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Parameters
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
bookRequired | string | The name of the book in the bible (e.g., Genesis) |
versionRequired | string | The Bible translation versionKJVASVBBEDarby |
chapterRequired | integer | The chapter number in the book range 1–∞ |
verseOptional | integer | The verse number in the chapter range 1–∞ |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"status": "ok",
"error": null,
"data": {
"text": "But with thee will I establish my covenant; and thou shalt come into the ark, thou, and thy sons, and thy wife, and thy sons' wives with thee.",
"book": "Genesis",
"abbr": "gn",
"chapter": 6,
"verses": [
18
],
"version": "KJV",
"testament": "Old Testament",
"bookNumber": 1,
"totalChapters": 50,
"totalVersesInChapter": 22,
"wordCount": 29
}
}Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
text | string | "But with thee will I establish my covenant; and thou shalt come into the ark, thou, and thy sons, and thy wife, and thy sons' wives with thee." | The complete text of the requested verse or passage |
book | string | "Genesis" | Full name of the biblical book (e.g., Genesis, Matthew) |
abbr | string | "gn" | Two-letter abbreviation of the book name |
chapter | number | 6 | Chapter number of the requested verse |
verses | array | [18] | Array of verse numbers included in the response |
version | string | "KJV" | Bible translation version (e.g., KJV, NIV, ESV) |
testament | string | "Old Testament" | Old Testament or New Testament classification |
bookNumber | number | 1 | Position of the book in the Bible (1-66) |
totalChapters | number | 50 | Total number of chapters in this book |
totalVersesInChapter | number | 22 | Total number of verses in the current chapter |
wordCount | number | 29 | Number of words in the returned verse(s) |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- Motivational Apps
- Use the Bible API to get bible verses for motivational apps. Use the data to inspire users, provide encouragement, and promote positivity
- Bible Study
- Use the Bible API to get bible verses for bible study. Use the data to read scripture, study the bible, and explore religious texts
- Devotional
- Get bible verses by using the Bible API for devotional purposes. Use the data to meditate on scripture, reflect on passages, and deepen spiritual practice
- Religious Education
- Access bible verses by using the Bible API for religious education. Use the data to teach scripture, share lessons, and engage students
Other ways to use Bible
Set up Bible on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Data Lookup: