API Base URL
Use this base URL for all public ScriptureFlow API requests:
https://scriptureflow-api-preview.pages.dev Use en-kjv, not kjv and not en-KJV.Build Bible apps, sermon preparation tools, devotional workflows, ministry automations, AI-assisted Scripture tools, and multilingual Scripture experiences using the ScriptureFlow public API.
Use this base URL for all public ScriptureFlow API requests:
https://scriptureflow-api-preview.pages.dev Use en-kjv, not kjv and not en-KJV.ScriptureFlow is a public Scripture access API and data layer for developers and ministries. It helps teams retrieve structured Scripture references without rebuilding a Scripture backend from scratch.
Understand what ScriptureFlow provides for ministries, apps, and developer platforms.
Open overviewReview public endpoint patterns, parameters, and response expectations.
Read specGet started quickly with validated URLs and language-specific examples.
Open quickstartBrowse translation/language availability for public use.
View languagesCopy ready-to-run request examples for common developer workflows.
View examplesUnderstand public terms and attribution expectations for API usage.
Read termsconst baseUrl = "https://scriptureflow-api-preview.pages.dev";
const url = `${baseUrl}/api/verse?version=en-kjv&reference=John%203%3A16`;
const data = await fetch(url).then((r) => r.json());
console.log(data);
import requests
base_url = "https://scriptureflow-api-preview.pages.dev"
url = f"{base_url}/api/verse?version=en-kjv&book=Amos&chapter=8&verse=4&end_verse=6"
response = requests.get(url, timeout=20)
print(response.json())
curl "https://scriptureflow-api-preview.pages.dev/api/verse?version=en-kjv&book=John&chapter=3&verse=16"
Runs two requests against the public API preview domain.
ScriptureFlow can be used inside agent workflows and AI-assisted tools where trustworthy Scripture retrieval matters.
Start with the endpoint specification and example requests, then add translation-aware selection using translations.json.
This portal documents public API usage only. It does not include private implementation guidance, internal operations details, or contributor-only instructions.
For integration feedback, start with the quickstart and endpoint specification, then verify translations with translations.json.
If a request fails, capture the exact URL and response status so your team can reproduce quickly.