Documentation for calling the API in Wordpress websites either by how to add the files or create the plugin.

When include-chapters is set to true then the individual chapter references should include a total_verses key. Knowing the total verses for each chapter can aid in validations on the client side and help stifle unnecessary calls to the api that would 404 if the wrong verse is entered in.

I'm aware that this has been requested before, but it seems there needs to be more detail to get any type of traction on implementation.

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.

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.

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.

It would be really good to see the 1984 NIV version in your API.

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

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.

A plain text option to retrieve text without any tags/xml

Add headers to support Cross-Origin Resource Sharing (CORS) for usage from client side javascript..

Current licensing only allows for non-commercial usage. This feature would support a paid model for use in commercial apps or websites.

Make NIV version available in the API. Although it would be nice to have free ministry use, open to paying a license fee if needed.

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.

Make NKJV version available in the API. Although it would be nice to have free ministry use, open to paying a license fee if needed.

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.

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!!!

It would be really good to see the tamil version in your api. Can you please let me know whether its possible.

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 :)