BibleHub APIbiblehub.com ↗
Access Strong's lexicon entries, interlinear verse analysis, morphology codes, and cross-references for Hebrew and Greek biblical texts via the BibleHub API.
What is the BibleHub API?
The BibleHub API exposes 9 endpoints covering Hebrew and Greek Strong's lexicon entries, word-by-word interlinear analysis, concordance data, and cross-references. Use get_hebrew_lexicon or get_greek_lexicon to retrieve original-script words, transliterations, part-of-speech tags, Brown-Driver-Briggs or Thayer's definitions, and NAS/Strong's Exhaustive definitions for any Strong's number. Interlinear endpoints break verses and full chapters into per-word morphology objects alongside KJV and ASV parallel text.
curl -X GET 'https://api.parse.bot/scraper/0a2a8344-f84d-41c5-9ec5-793cc6306540/get_hebrew_lexicon?strongs_number=430' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieve detailed Hebrew lexicon data for a given Strong's number. Returns the original Hebrew word, morphology, definitions from Strong's Exhaustive Concordance and NAS, Brown-Driver-Briggs entry, word origin, and concordance usage examples. Numbers range from 1 to approximately 8674.
| Param | Type | Description |
|---|---|---|
| strongs_numberrequired | string | Strong's Hebrew number (e.g., 1, 430, 2617) |
{
"type": "object",
"fields": {
"language": "string, always 'hebrew'",
"concordance": "array of objects with 'reference' and 'text' keys",
"definitions": "object with optional keys 'nas' and 'strongs_exhaustive' containing definition text",
"word_origin": "string, etymology and origin information",
"original_word": "string, Hebrew word in original script",
"pronunciation": "string",
"part_of_speech": "string, grammatical category",
"strongs_number": "string, the requested Strong's number",
"lexical_summary": "string, brief word summary",
"transliteration": "string, romanized form",
"phonetic_spelling": "string",
"brown_driver_briggs": "string, BDB lexicon entry text"
},
"sample": {
"data": {
"language": "hebrew",
"concordance": [],
"definitions": {
"nas": "Word Origin pl. of eloah Definition God, god",
"strongs_exhaustive": "angels, exceeding, God, very great, mighty"
},
"word_origin": "[plural of H433]",
"original_word": "אֱלהִים",
"pronunciation": "eh-lo-HEEM",
"part_of_speech": "Noun Masculine",
"strongs_number": "430",
"lexical_summary": "elohim: God, gods, divine beings, judges",
"transliteration": "elohiym",
"phonetic_spelling": "(el-o-heem')",
"brown_driver_briggs": "noun masculine plural"
},
"status": "success"
}
}About the BibleHub API
Lexicon Endpoints
get_hebrew_lexicon and get_greek_lexicon each accept a single strongs_number and return a structured object containing original_word (in Hebrew or Greek script), transliteration, pronunciation, part_of_speech, word_origin, and a lexical_summary. The definitions object carries up to two keys — nas (NAS Exhaustive Concordance) and strongs_exhaustive — while Hebrew entries also include Brown-Driver-Briggs data and Greek entries include Thayer's Greek Lexicon text. A concordance array lists Bible references and verse snippets showing the word in context. Batch variants (batch_hebrew_lexicon, batch_greek_lexicon) accept up to 100 Strong's numbers per call; any individual lookup failure is recorded in a skipped array rather than aborting the whole request. An optional fields parameter limits which keys are returned per entry.
Interlinear Endpoints
get_interlinear_verse takes book, chapter, and verse and returns a words array where each element carries strongs_number, word (original script), transliteration, english gloss, and a morphology code string. The response also includes kjv_text and asv_text for the full verse. The language field is hebrew for Old Testament books and greek for New Testament books, determined automatically from the book name. get_interlinear_passage works at the chapter or verse-range level, returning an array of verse objects each with the same structure. get_interlinear_book iterates entire chapters and returns simplified word data (Strong's number, original script, transliteration, English gloss) plus KJV text; a skipped_chapters array reports any chapters that could not be retrieved.
Search and Cross-References
search_lexicon accepts a free-text query (e.g., "grace", "father") and an optional language filter of hebrew or greek, returning an array of matching Strong's entries with strongs_number, text, and summary. Results are ordered by relevance. get_cross_references takes a single verse address (book, chapter, verse) and returns a references array listing each related passage with its target book name, chapter, verse number, and the full reference string as displayed on BibleHub.
Coverage Notes
Hebrew Strong's numbers run from 1 to approximately 8,674; Greek numbers run from 1 to approximately 5,624. Book names follow BibleHub conventions, and multi-word book names use underscores (e.g., 1_Samuel, Song_of_Solomon). Morphology codes in interlinear responses follow standard grammatical tagging conventions but are returned as raw strings — parsing them requires knowledge of the relevant tagging scheme.
The BibleHub API is a managed, monitored endpoint for biblehub.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when biblehub.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official biblehub.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a Bible study tool that displays Strong's definitions and concordance usage for any word a reader taps
- Generate word-frequency statistics across an entire book using
get_interlinear_bookand the per-wordstrongs_numberfields - Compare NAS and Strong's Exhaustive definitions side-by-side for Hebrew or Greek terms using the
definitionsobject - Populate a cross-reference sidebar in a Bible reader app using
get_cross_referencesfor each displayed verse - Create a morphology drill app that quizzes users on grammatical codes returned in interlinear
wordsarrays - Batch-resolve a list of Strong's numbers from a commentary index using
batch_greek_lexiconorbatch_hebrew_lexiconwith field filtering - Build a lexicon search feature that surfaces relevant Strong's entries by meaning or transliteration via
search_lexicon
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does BibleHub have an official developer API?+
What does the `get_interlinear_verse` endpoint return beyond the translated text?+
words array where each entry carries the original Hebrew or Greek script (word), transliteration, english gloss, a morphology code string, and the associated strongs_number. The response also includes the complete kjv_text and asv_text for the verse, and a language field indicating whether the source text is Hebrew or Greek.Does the batch lexicon endpoint return full entries or a summary?+
get_hebrew_lexicon or get_greek_lexicon. You can pass a fields array to limit the response to specific keys such as original_word, transliteration, or definitions, which reduces payload size when you only need a subset.Are Bible translations other than KJV and ASV available in interlinear responses?+
kjv_text and asv_text fields only. Cross-reference and lexicon endpoints do not return translation text at all. You can fork this API on Parse and revise it to add additional translation fields if BibleHub exposes them for the passages you need.