biblehub.com APIbiblehub.com ↗
Access Strong's Hebrew and Greek lexicon entries, interlinear verse analysis, and morphology data from BibleHub via a structured JSON API.
curl -X GET 'https://api.parse.bot/scraper/0a2a8344-f84d-41c5-9ec5-793cc6306540/get_hebrew_lexicon?strongs_number=2617' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieve detailed Hebrew lexicon data for a given Strong's number. Includes summary, original word, morphology, definitions from Strong's Exhaustive Concordance and NAS (when available), Brown-Driver-Briggs entry, and usage examples (concordance).
| 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": {
"strongs_exhaustive": "favor, good deed, kindly, loving-kindness, merciful kindness, mercy, pity, reproach, wicked thing..."
},
"word_origin": "[from H2616] 1. kindness 2. (by implication, towards God) piety...",
"original_word": "חֵסֵד",
"pronunciation": "kheh'-sed",
"part_of_speech": "Noun Masculine",
"strongs_number": "2617",
"lexical_summary": "checed: Lovingkindness, mercy, steadfast love, loyalty, faithfulness, goodness",
"transliteration": "checed",
"phonetic_spelling": "(kheh'-sed)",
"brown_driver_briggs": "חֶ֫סֶד : 247 noun masculine 2Samuel 16:17 goodness, kindness..."
},
"status": "success"
}
}About the biblehub.com API
The BibleHub API exposes 4 endpoints for retrieving biblical language data, including full Hebrew and Greek lexicon entries keyed by Strong's number, word-by-word interlinear analysis for any Old or New Testament verse, and keyword-based lexicon search. The get_interlinear_verse endpoint returns a words array with individual Strong's numbers, transliterations, English glosses, and morphology codes for every word in a specified chapter, verse, and book.
Lexicon Lookup
get_hebrew_lexicon and get_greek_lexicon each accept a Strong's number and return a consistent set of fields: original_word in the source script, transliteration, pronunciation, part_of_speech, word_origin, lexical_summary, and a definitions object that may include both nas (New American Standard) and strongs_exhaustive definition text. Hebrew entries include data drawn from the Brown-Driver-Briggs lexicon; Greek entries include Thayer's Greek Lexicon material. Both endpoints also return a concordance array of {reference, text} pairs showing real verse occurrences of the word.
Interlinear Verse Analysis
get_interlinear_verse takes book, chapter, and verse as inputs and returns a words array where each element carries strongs_number, word (original script), transliteration, english, and morphology. The language field in the response is 'hebrew' for Old Testament books and 'greek' for New Testament books, so a single endpoint covers the full canon. Books with spaces in their names use underscore notation in the book parameter (e.g., 1_Samuel).
Lexicon Search
search_lexicon accepts a query string and an optional language filter ('hebrew' or 'greek'). It returns a results array of objects with strongs_number, text, and summary, making it useful for discovering Strong's numbers when you only know an English gloss or approximate transliteration. Omitting language returns matches across both language corpora.
- Build a Bible study tool that displays original-language word definitions inline alongside English translations using
get_interlinear_verse. - Populate a flashcard app with Hebrew or Greek vocabulary by pulling
original_word,transliteration, anddefinitionsfrom the lexicon endpoints. - Cross-reference how a specific Strong's word (e.g., H2617, 'hesed') is used across the Old Testament via the
concordancearray. - Generate morphology breakdowns for seminary students by iterating
get_interlinear_verseacross a passage and groupingmorphologycodes. - Resolve an English keyword like 'grace' to its underlying Greek Strong's entries using
search_lexiconbefore fetching full definitions. - Build a word-frequency tool by collecting
strongs_numbervalues across multiple interlinear verses and aggregating counts. - Power a language-learning interface showing
part_of_speech,word_origin, andlexical_summaryfor any Strong's entry the user looks up.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. 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 `words` array in `get_interlinear_verse` actually contain?+
words includes strongs_number, word (the token in Hebrew or Greek script), transliteration, english (the English gloss for that token), and morphology (a coded string indicating grammatical properties like tense, person, case, or stem). The top-level language field tells you whether the verse is analyzed as Hebrew or Greek.Are both NAS and Strong's Exhaustive definitions always present in lexicon responses?+
definitions object has optional keys: nas and strongs_exhaustive are included when that source material is available for the given Strong's entry. Some entries may have only one or neither key populated. The lexical_summary field provides a brief definition that is consistently present.Does the API support looking up verses by passage range, such as an entire chapter at once?+
get_interlinear_verse accepts a single book, chapter, and verse combination and returns one verse at a time. To cover a full chapter, you would need to call the endpoint once per verse. You can fork this API on Parse and revise it to add a chapter-range endpoint that iterates verses and returns a collected response.Does the API expose audio pronunciation files or parsing tables beyond the morphology code string?+
pronunciation string (text representation), not an audio file. Morphology is returned as a coded string in the morphology field of interlinear word objects; the API does not expand those codes into human-readable parsing tables. You can fork the API on Parse and revise it to decode morphology codes into structured labels.