Bible Search API
-
Return multiple verses in a single call
Hello, it would be great if the API could return multiple verses in one call. For instance, /bibles/[id]/verses/[PSA.1.1,PSA.1.2] rather than two separate calls. This would reduce server load and lag if you're trying to grab a passage or series of verses.
3 votes -
More specific documentation on formatting calls
A list of the actual IDs for the Bible Editions, and specific guidance on how to format requests for passages, properly abbreviate bible versions, a list of the IDs used for the different bible editions, etc. would be a GREAT help. I appreciate the existing documentation, it gets you right through credentialing which I personally find to be the most difficult part of API calls (especially if you are not using cURL or related services), and it is good for certain "plug and play" uses. But I want to feed users specific verse selections, and the existing documentation is silent…
1 vote -
Serve the FUMS script over https
FUMS script is being blocked from loading in my Angular 7 app due to
this error: "Mixed Content: The page at 'https://...'; was loaded over HTTPS, but requested an insecure script 'http://cdn.scripture.api.bible/fums/fumsv2.min.js'. This request has been blocked; the content must be served over HTTPS.3 votes -
ESV version gone
Today I noticed that the ESV version was missing from the API. It is my favorite version, so I'm very sad to see it gone.
7 votes -
Insert API key directly into URL
Most APIs allow for the insertion directly into the URL string. This would make it easy to use in native iOS apps. As it is today, the use of the API key is complex. I see no examples of how to code this for native iOS apps in Swift 3.0
6 votes -
Add NLT (New Living Translation)
Make NLT version available in the API. Although it would be nice to have free ministry use, open to paying a license fee if needed.
29 votes -
Do not change the format without increasing the version number
In the past titles were identified with something like span class='title-passage', now it's a h3 tag. Please do not make such changes, without notice, this makes my client crashing.
1 vote -
Url for Audio
Thank you for your great effort and contribution with the word of God. The audio is not in the documentation. I not sure if exist or i have to call an extra web api, please can you clarify that. God Bless YOU!!!
1 vote -
Add a tamil version to your API
It would be really good to see the tamil version in your api. Can you please let me know whether its possible.
15 votes -
3 votes
-
Please fix: it's impossible to get 36 chapter using API
If you use such url: https://bibles.org/v2/passages.js?q[]=2Chr36&version=eng-MSG&include_marginalia=true&lang=nl
than you will get 500 status (Internal Server Error).
Also you can try to change a numbers of chapters and verses (because 35:26 and 36:1 are combined and appears to be a single verse).
I tried to use such combinations: 35:26-36:23 and similar to them.
Please fix bug inside your backend part :)9 votes -
Retrieve Verse Count per Chapter for Entire Bible (to Support a Verse Chooser UI)
I would like to retrieve the verse count for each chapter in an entire bible version.
Basically, I need a list of books, chapters, and verse count in each chapter.
This is needed to build a verse chooser UI, where the user can choose the book, chapter, and verse before any additional api request is made.
Also, since each book can have it's own versification using a generic verse count does not always work.
By making a specific api endpoint for this purpose, it would be easy to cache and make efficient on both sides. (Right now I have to…
1 vote -
Either use standard ISO language codes or provide a way of getting the names of the language codes you use.
There currently doesn't seem to be a documented way of getting the names of the languages for each version of the bible, nor of getting the full list of languages you support. This makes it hard to provide a UI where a user selects their language followed by a specific version.
4 votes -
Add the 1984 NIV bible to your API.
It would be really good to see the 1984 NIV version in your API.
13 votes -
Add german versions of the bible
So many versions available but not a single one in German!
Ideally you could integrate Luther 2017 or Schlachter 2000 translations.If you would do this, you would be the only service to provide an API for the German Bible
4 votes -
Create example code to use the API in c#
It would be great to have official or community supported examples of how to the use the API in C# (.NET). Code samples or reference implementations would optimally cover how to handle authentication, fetching content and complying with the FUMS reporting.
2 votes -
Add RNKSV and NKRV version
kor-NKRV and kor-RNKSV are available at bibles.org. Could you add these versions into the API. Especially, NKRV is the most popular bible version in Korea. Thanks for your consideration.
1 vote -
Query usage statistics
The API limits to 5000 queries/day. Current usage of the month should be available to the developer.
5 votes -
Allow for full bible downloads
Allow the developer to download the full bible json/xml by version key instead of by chapter. I think this would make it nicer for offline support of applications.
23 votes -
Fix broken references (eng-GNTD:Zech.4.10b, eng-GNTD:Matt.1.6b, eng-GNTD:Mark.16.9)
If you walk through verse by verse, the next verse pointer points to these IDs, but they do not exist. If you walk backwards using previous, they are still pointed to, but they do not exist.
1 vote
- Don't see your idea?