Bible

Overview

A Bible verse and scripture API. 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.

Live Test Bible API →

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.

1
2

curl "https://api.apiverve.com/v1/bible?book=Genesis&version=KJV&chapter=5&verse=17&verseEnd=18" \
  -H "x-api-key: your_api_key_here"

1
2
3
4
5
6
7
8

const res = await fetch('https://api.apiverve.com/v1/bible?book=Genesis&version=KJV&chapter=5&verse=17&verseEnd=18', {
  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);

1
2
3
4
5
6
7
8
9
10

import requests

res = requests.get(
    "https://api.apiverve.com/v1/bible?book=Genesis&version=KJV&chapter=5&verse=17&verseEnd=18",
    headers={"x-api-key": "your_api_key_here"},
    timeout=15,
)
res.raise_for_status()

print(res.json()["data"])

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

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&verseEnd=18", 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.

Parameters

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.

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.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45

{
  "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. And of every living thing of all flesh, two of every sort…",
    "book": "Genesis",
    "abbr": "Ge",
    "chapter": 6,
    "verses": [
      18,
      19
    ],
    "version": "KJV",
    "testament": "Old Testament",
    "bookNumber": 1,
    "totalChapters": 50,
    "totalVersesInChapter": 22,
    "wordCount": 58,
    "reference": "Genesis 6:18-19",
    "passage": [
      {
        "chapter": 6,
        "verse": 18,
        "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."
      },
      {
        "chapter": 6,
        "verse": 19,
        "text": "And of every living thing of all flesh, two of every sort shalt thou bring into the ark, to keep them alive with thee; they shall be male and female."
      }
    ],
    "previous": {
      "reference": "Genesis 6:17",
      "book": "Genesis",
      "chapter": 6,
      "verse": 17
    },
    "next": {
      "reference": "Genesis 6:20",
      "book": "Genesis",
      "chapter": 6,
      "verse": 20
    }
  }
}

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.

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.

Use cases

Daily Devotional Notifications

Devotional mobile apps schedule daily morning push notifications that display a random verse along with its book and chapter reference.

Worship Slide Generation

To prepare church projection slides, presentation software queries chapter text and verse numbers to format reading prompts automatically.

Multitranslation Scripture Study

Academic study platforms pull the same verse across KJV, BSB, YLT and Darby so researchers can compare wording line by line.

Custom Journal Publishing

When laying out printable prayer planners, publishing tools inject verse text and testament classifications into daily reading header blocks.

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: