No Official API Exists

There Is No Official Bible Gateway API

If you need structured Scripture data for an application, backend service, or AI workflow, use a versioned JSON Bible API built for production systems.

Get free API key View API docs

Free tier available — no credit card required. 10 public-domain versions. Versioned endpoints.


Why Scraping Website Content Fails in Production

HTML layout may change without notice, silently breaking your app
No versioned API contract or schema guarantees
DOM selector logic becomes permanent maintenance debt
No structured identifiers for canonical verse references

Websites are optimized for human browsing. Production systems require predictable, structured data contracts.


Website Access vs Structured Bible API

Aspect Website Content BibleBridge JSON API
Audience Human readers Applications & backend systems
Format HTML markup Structured JSON
Schema Stability No guarantees Versioned response schema
Reference Handling Implicit in layout Canonical book & verse identifiers
Automation Requires scraping logic Designed for programmatic access

Example Request

curl --get https://holybible.dev/api/passage \
  -H "Authorization: Bearer YOUR_API_KEY" \
  --data-urlencode ref="john3:16" \
  --data version=KJV

{
  "status": "success",
  "type": "single",
  "version": "KJV",
  "osis_id": "John.3.16",
  "results_count": 1,
  "verse_units": 1,
  "data": [
    {
      "book": "John",
      "chapter": 3,
      "verse": 16,
      "text": "For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life."
    }
  ]
}

Start Building With a Production-Ready Bible API

Structured JSON. Stable schema. Free tier available — no credit card required.

Get your free API key View API docs