🌊 ScriptureFlow API Preview • Multilingual Scripture data for builders

ScriptureFlow API Preview

ScriptureFlow transforms a large multilingual Scripture corpus into clean, structured, API-ready JSON for developers, ministries, educators, researchers, and faith-based technology builders.

Try it now Developer Docs View translations.json View public catalog View build status

What is ScriptureFlow?

ScriptureFlow is not a single consumer Bible app. It is a Scripture data infrastructure project. Its purpose is to help developers build Bible-centered apps, study tools, devotionals, AI-assisted ministry resources, educational tools, and multilingual Scripture experiences without rebuilding the same Scripture data layer from scratch.

This preview exposes generated JSON output from the ScriptureFlow pipeline. The raw source corpus contains millions of structured files. ScriptureFlow audits, validates, catalogs, and converts that source data into simpler API-ready files that developers can fetch directly.

Try it now

Choose an endpoint, run a live request, inspect the JSON response, and copy starter code. This runs directly against the deployed ScriptureFlow preview.

Copy starter code

Response

Click “Run request” to see a live API response.

Who is this for?

  • Developers building Bible apps and Scripture tools
  • Ministries creating digital discipleship resources
  • Educators building Scripture-based learning tools
  • Researchers working with multilingual Bible data
  • Faith-based builders exploring AI-ready Scripture workflows

Why does it exist?

Many Bible technology projects need structured Scripture data, but the raw data can be difficult to normalize, validate, index, and serve. ScriptureFlow exists to make that foundation easier, especially for multilingual and underrepresented language communities.

The goal is simple: make Scripture easier to build with, across more languages and more communities.

Available endpoints

These are static JSON endpoints plus a simple lookup function. No API key is required for this preview.

Catalog and status

/translations.json /public-catalog.json /status.json

Runtime API endpoints

/api/verse?version=en-lsv&book=john&chapter=3&verse=16 /api/verse?version=en-lsv&book=amos&chapter=8&verse=4&end_verse=6 /api/verse?version=en-lsv&reference=Amoso%208%3A4-6 /api/quick-verse?version=en-kjv

/api/verse performs a runtime lookup for a specific reference or passage. /api/quick-verse returns a runtime-selected verse from the requested translation. Refreshing Quick Verse can return a different verse.

Per-translation files

/[version]/translation.json /[version]/books.json /[version]/chapters.json /[version]/verses-index.json /[version]/random.json

Each public translation includes a generated Verse of the Day at /[version]/random.json. This is a static generated JSON file that updates when the ScriptureFlow generator runs. It does not return a new random verse on every refresh.

Verse of the Day is generated separately for each translation because Bible translations may differ in canon, book availability, chapter divisions, and verse numbering. ScriptureFlow uses each translation’s own available verse index instead of forcing one shared reference across every translation.

For large translations, /[version]/verses-index.json may return a split-index manifest with part files instead of one huge array. The /api/verse endpoint hides that complexity.

Need a new verse on every request? Use /api/quick-verse?version=[version]. The current /[version]/random.json file remains the translation-scoped Verse of the Day.

What is included now?

The current preview focuses on generated catalog and translation-level output.

Translation catalog Public status file Books index Chapters index Verses index Translation-scoped Verse of the Day Quick Verse runtime endpoint Split-index handling Simple verse lookup Verse range lookup Failed translation exclusion

What is coming next?

  • Expanded developer documentation and examples
  • Improved public catalog metadata
  • Standardized response metadata across lookup and generated endpoints
  • Translation availability and licensing metadata
  • Search-friendly and AI-ready indexing improvements
  • Custom domain support
  • Expanded multilingual quality checks

Important note on translation rights

ScriptureFlow separates technical readiness from publication rights. A translation may be structurally ready while still requiring review for licensing, copyright, or redistribution permissions. Public deployment should prioritize translations that are permitted for open distribution.

Project purpose

ScriptureFlow exists to support Gospel-centered technology by making structured Scripture data easier to access, easier to validate, and easier to build with across languages.

Build tools. Support ministry. Serve more languages.