Please fill in this page so I don't have to hit the API every time I want to quickly look up a book id https://docs.api.bible/guides/books

Add common reading plans such as M'Cheyne One Year Reading Plan, Chronological Reading Plan, Etc.

Currently, a sections can be retrieved per book, i.e.: ​/v1​/bibles​/{bibleId}​/books​/{bookId}​/sections We would love to have an API endpoint that retrieves all the sections for a single bibleID in one call. Patrick - Netherlands Bible Society

Like many other available versions here, Chinese Union Version is available in https://ebible.org/download.php . In particular, "Chinese Union Version (traditional)" & "Chinese Union Version (simplified)" are the 2 variants provided. Please consider adding these as well. Thanks.

@bryce This request is a follow-up on https://apibible.canny.io/feature-requests/p/parallel-verse-requests-for-bridged-verses We are running into some problems with the ‘parallels’ function of API.Bible . It appears that when we use parallels on the verse-endpoint, it has unexpected behavior (or a bug?). It works well when the requested verse is available in all parallel bibles. If it is not available in one of the parallels, the whole requests returns an error. reasons are for example when the whole book is not available in a parralel. Example with DC books: https://api.scripture.api.bible/v1/bibles/a31452bf933bcd2d-01/verses/WIS.15.11?content-type=json&parallels=173b6ec5bba026d2-01,87f620660790371b-01 example for a whole testament not available, like only having the OT in the BHS: https://api.scripture.api.bible/v1/bibles/a31452bf933bcd2d-01/verses/MAT.1.1?content-type=json&parallels=218a38697cbf2486-01

https://docs.api.bible/tutorials/demo-intro The link for How we built it in the demo app section of the documentation is broken. I would be interested in this documentation.

Can you please update the documentation page for the "search" function? Right now it just says "Stuff goes here" or something and I can only determine so much from the api itself. Thanks!

Currently the API is only set up for non-commercial usage. Enable paid subscription models for commercial usage.

I would like to be able to receive plain-text verses when calling /query. When calling /verses, this can be accomplished by passing a content-type query parameter. As far as I can tell, content-type doesn't seem to be supported by /query, though. It would be a useful addition!

I want an API that returns three-letter codes that your library has. This is not a request, but a question. Is the three-letter codes you use is macrolanguage or individual languages those are member of a macrolanguage?