Overview

API.Bible aggregates over 2,500 Bible versions across 1,600+ languages from the American Bible Society. It provides structured access to passages, verses, chapters, and search.

Beginner Tip

Register for a free API key at https://scripture.api.bible, then fetch a verse with the /bibles/{bibleId}/verses/{verseId} endpoint. Use the /bibles endpoint first to find valid Bible IDs for your language.

Available Data

The kind of data this API exposes, based on its documentation. We could not call the endpoint to confirm the exact field names.

The Bible data via REST API

Example Response

Illustrative shape only — we were not able to call this endpoint (it requires credentials or exposes no public sample URL), so the fields below show the kind of data this API returns rather than a recorded response.

JSON Response · Illustrative
{
  "status": "success",
  "data": {
    "result": "Data from The Bible",
    "description": "Everything you need from the Bible in one discoverable place",
    "timestamp": "2025-01-15T10:00:00Z"
  }
}

Field Reference

data.id Unique verse identifier in book.chapter.verse format, e.g. "JHN.3.16".
data.reference Human-readable reference string, e.g. "John 3:16".
data.content Verse text (plain text or HTML depending on content-type param).
data.verseCount Number of verses in the response (useful for passage requests).
data.copyright Copyright notice for the Bible version being accessed.

Implementation Example

Calls a real endpoint of this API. Replace any placeholder credentials with your own key.

Request
const url = "https://api.scripture.api.bible/v1/bibles/de4e12af7f28f599-02/verses/JHN.3.16?content-type=text";
// Replace headers or query params with the values required by this API.
const response = await fetch(url, {
  headers: {
  "X-API-Key": "YOUR_API_KEY"
  }
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

Generated guidance based on this API's documentation, not observed by us. Treat it as a starting point and check against the provider's own error reference.

HTTP 401 Unauthorized Missing or incorrect api-key header
Add the header -H "api-key: YOUR_KEY" to every request. The key goes in a custom header, not as a query parameter.
HTTP 404 on verse ID Verse ID format is incorrect (must be e.g. "JHN.3.16")
Use the /bibles/{bibleId}/books and /chapters endpoints to navigate to valid IDs before fetching verses.
Response "content" contains HTML tags Default response wraps verse text in OSIS-style markup
Add ?content-type=text to the query string to receive plain text instead of tagged HTML.

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

Technical Specifications

Auth API Key
HTTPS REQUIRED
CORS UNKNOWN
Category Books
Difficulty Intermediate
Listing details not endpoint-verified

Related Tags

Similar APIs

View All →