BibleHub APIbiblehub.com ↗
Access Strong's Hebrew and Greek lexicon entries, interlinear verse analysis, morphology codes, and concordance data from BibleHub via a structured JSON API.
What is the BibleHub API?
This API exposes 8 endpoints covering Hebrew and Greek biblical lexicon data from BibleHub, including word-level interlinear analysis, Strong's concordance definitions, morphology codes, and multi-source definitions (NAS, Brown-Driver-Briggs, Thayer's). The get_interlinear_verse endpoint returns every word in a verse with its Strong's number, transliteration, English gloss, and morphology code alongside full KJV and ASV verse 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 Lookups
get_hebrew_lexicon and get_greek_lexicon each accept a Strong's number and return the original-script word, transliteration, pronunciation, part of speech, etymology (word_origin), a lexical_summary, and definitions from up to two sources: nas (NAS Exhaustive Concordance) and strongs_exhaustive. Hebrew entries include Brown-Driver-Briggs data; Greek entries include Thayer's Greek Lexicon. Both endpoints also return a concordance array of {reference, text} objects showing real biblical usages. Hebrew numbers run roughly 1–8674; Greek numbers run roughly 1–5624.
Interlinear Analysis
get_interlinear_verse takes a book, chapter, and verse and returns a words array where each element carries strongs_number, word (original script), transliteration, english (gloss), and morphology (grammatical code). The language field is 'hebrew' for Old Testament books and 'greek' for New Testament books. Full kjv_text and asv_text strings are returned alongside the word-level data.
get_interlinear_passage extends this to a verse range or full chapter using optional verse_start and verse_end parameters. get_interlinear_book spans one or more chapters via chapter_start and chapter_end; it returns simplified word data (Strong's number, original script, transliteration, English gloss) and kjv_text per verse, plus a skipped_chapters array for any chapters that failed after retries.
Batch and Search
batch_hebrew_lexicon and batch_greek_lexicon accept a strongs_numbers array of up to 100 entries and return all corresponding lexicon objects in one call. An optional fields parameter narrows the response to specific keys, reducing payload size. Entries that fail individually are listed in a skipped array rather than failing the entire request. search_lexicon accepts a free-text query and optional language filter ('hebrew' or 'greek'), returning a results array of {strongs_number, text, summary} objects ordered by relevance.
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 Strong's concordance browser that links every word in a verse to its full lexicon entry via
get_interlinear_verseandget_hebrew_lexicon. - Generate morphological frequency tables for a book by running
get_interlinear_bookand aggregating themorphologycodes across all words. - Populate a Bible study app's tooltip with etymology and multi-source definitions using the
word_originanddefinitionsfields fromget_greek_lexicon. - Cross-reference Brown-Driver-Briggs and NAS definitions for a set of Hebrew root words in bulk using
batch_hebrew_lexiconwithfieldsfiltering. - Search for all Strong's entries related to a theological concept (e.g., 'grace' or 'covenant') using
search_lexiconand display matching concordance verses. - Produce parallel KJV/ASV chapter displays with word-level Strong's annotations using
get_interlinear_passageover a chapter range. - Audit transliteration consistency across a vocabulary list by batch-fetching Greek entries and comparing the
transliterationandpronunciationfields.
| 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 morphology data does `get_interlinear_verse` return, and how is it formatted?+
words array includes a morphology field containing a coded string (e.g., 'V-QAL-Perf-3ms' for Hebrew or 'V-AAN' for Greek). These codes follow standard grammatical tagging conventions used in biblical language tools. The endpoint does not expand the codes into plain-English labels; your application would need to decode them against a morphology key.Does the API return deuterocanonical or apocryphal books?+
What happens if a Strong's number has no entry or a verse fails to load in a batch call?+
batch_hebrew_lexicon and batch_greek_lexicon, any number that fails to resolve is added to the skipped array in the response rather than causing the whole call to fail. For get_interlinear_book, chapters that fail after retries appear in skipped_chapters. Individual get_hebrew_lexicon or get_greek_lexicon calls for an out-of-range or non-existent number will return an error.