I'm fairly confident the text is parsed properly to json but if it isn't then just shoot a PR in or something. Hopefully nothing is missing though.
Open openapi.yaml
in your favorite tool(s) such as Insomnia or the Swagger Online Editor to see and try out all the endpoints.
If the service is down (because I stopped hosting it) change the servers section to your own servers or local instance. You might need to put some extra work in for https support in your local instance.
servers:
- url: 'http://localhost:8080/api'
description: 'No SSL'
# - url: 'https://kjb.heckin.dev/api'
# description: 'SSL'
{
"titles": [
{
"title": string,
"alt": string
}
],
"books": [
{
"title": string,
"alt": string,
"chapters": [
{
"chapter": int
"verses": [string]
}
]
}
]
}
The raw utf-8 content for the King James Bible (kjv/kjb) was acquired from The Project Gutenberg eBook of The King James Bible. This can be seen within the files named kjv-new.[txt/json]
and kjv-old.[txt/json]
which have been modified for parsing.
See their license at the bottom of the file for information about their license if you plan to use/distribute/sell any part(s) of this codebase using their text.