The Nusantara Bible REST API is a service designed to provide quick and easy access to Bible texts in various translated versions. With this API, developers can integrate Bible texts into their applications or websites, allowing users to read, search, or display specific verses and chapters as needed. This API uses the JSON data format, which makes it easy to process and present Bible data in modern applications.
The Nusantara Bible REST API data source comes from SABDA Labs, a digital research platform that provides Bible resources and Christian literature for the needs of developers and technology users. With this API, you can access Bible texts based on books, chapters, verses, and translated versions, including the New Testament (NT), King James Version (KJV), and others.
The Nusantara Bible REST API is also very useful for developers of spiritual applications, such as digital Bible readers, daily devotions, or theological study tools. This API allows applications to present relevant Bible data, such as the full text of chapters, specific verses, or search results related to specific themes. With a fast response and easy-to-process data format, this API is a very helpful tool in developing Bible-based digital solutions.
The simplicity and flexibility of the Nusantara Bible REST API makes it an ideal choice for a variety of use cases. From mobile apps to church websites, this API provides a powerful solution for providing access to God's Word in a modern, structured way. Whether you're a developer creating Bible study tools, or an organization looking to provide digital access to sacred texts, the Nusantara Bible REST API offers capabilities that can be tailored to your needs.
This request retrieves all data from the Old Testament and the New Testament. which includes Genesis through Revelation.
[
{
"id": 1,
"short": "Kej",
"name": "Kejadian",
"chapter": 50
},
{
"id": 2,
"short": "Kel",
"name": "Keluaran",
"chapter": 40
}
]
curl --location --request GET 'https://zylalabs.com/api/6657/indonesia+bible+api/9772/all+bible+lists' --header 'Authorization: Bearer YOUR_API_KEY'
This request calls for Bible data or lists from the Old Testament from Genesis to Malachi.
[
{
"id": 1,
"short": "Kej",
"name": "Kejadian",
"chapter": 50
},
{
"id": 2,
"short": "Kel",
"name": "Keluaran",
"chapter": 40
}
]
curl --location --request GET 'https://zylalabs.com/api/6657/indonesia+bible+api/9773/list+of+old+bibles' --header 'Authorization: Bearer YOUR_API_KEY'
This request calls for data or a list of Bibles from the New Testament from Matthew to Revelation.
[
{
"id": 40,
"short": "Mat",
"name": "Matius",
"chapter": 28
},
{
"id": 41,
"short": "Mar",
"name": "Markus",
"chapter": 16
}
]
curl --location --request GET 'https://zylalabs.com/api/6657/indonesia+bible+api/9774/list+of+new+bibles' --header 'Authorization: Bearer YOUR_API_KEY'
This Endpoint retrieves all Book Names, Book Titles, Verse Contents and Article Numbers.
{
"book_id": "1",
"book_name": "Kejadian",
"book_title": "Kejadian 1:1-31",
"verses": [
{
"verse": "1",
"text": "Pada mulanya Allah menciptakan langit dan bumi.",
"title": "Allah menciptakan langit dan bumi serta isinya"
},
{
"verse": "2",
"text": "Bumi belum berbentuk dan kosong; gelap gulita menutupi samudera raya, dan Roh Allah melayang-layang di atas permukaan air."
}
]
}
curl --location --request GET 'https://zylalabs.com/api/6657/indonesia+bible+api/9776/bible+content' --header 'Authorization: Bearer YOUR_API_KEY'
In Enpoint, it takes all Book Names, Book Titles, Verse contents and Chapter Numbers, by adding Bible Translation versions such as TB, TL, AV, and others.
{
"book_id": "1",
"book_name": "Kejadian",
"book_title": "Kejadian 1:1-31",
"verses": [
{
"verse": "1",
"text": "Pada mulanya Allah menciptakan langit dan bumi.",
"title": "Allah menciptakan langit dan bumi serta isinya"
},
{
"verse": "2",
"text": "Bumi belum berbentuk dan kosong; gelap gulita menutupi samudera raya, dan Roh Allah melayang-layang di atas permukaan air."
}
]
}
curl --location --request GET 'https://zylalabs.com/api/6657/indonesia+bible+api/9777/bible+version+content' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
Each endpoint returns structured data related to Bible texts. For example, the "GET All Bible Lists" endpoint provides a list of books from both the Old and New Testaments, while the "GET Bible Content" endpoint returns detailed verse content, including book names and titles.
Key fields include "id," "short," "name," and "chapter" for book lists, and "book_id," "book_name," "book_title," "verse," and "text" for verse content. These fields help identify and organize the Bible texts effectively.
The response data is organized in JSON format, with each endpoint returning an array or object containing relevant fields. For instance, the "GET Bible Content" endpoint returns an object with book details and an array of verses, making it easy to parse and display.
Each endpoint provides specific information: "GET All Bible Lists" offers a comprehensive list of all books, while "GET Bible Version Content" includes translations and verse details. This allows users to access both general and specific Bible data.
Users can customize requests by specifying parameters such as book names or translation versions in endpoints like "GET Bible Version Content." This allows for tailored responses based on user needs, such as retrieving specific translations.
Typical use cases include developing digital Bible readers, creating daily devotion apps, or building theological study tools. The API's structured data supports various applications, enabling users to access and display Bible texts effectively.
The data is sourced from SABDA Labs, a digital research platform that provides Bible resources and Christian literature. This ensures that the API delivers reliable and accurate Bible texts for developers and users.
Data accuracy is maintained through regular updates and quality checks by SABDA Labs. This process ensures that the Bible texts provided via the API are consistent with established translations and scholarly standards.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
2,033ms
Service Level:
100%
Response Time:
1,412ms
Service Level:
100%
Response Time:
99ms
Service Level:
100%
Response Time:
1,622ms
Service Level:
100%
Response Time:
754ms
Service Level:
100%
Response Time:
135ms
Service Level:
100%
Response Time:
3,035ms
Service Level:
100%
Response Time:
785ms
Service Level:
100%
Response Time:
7,645ms
Service Level:
100%
Response Time:
478ms
Service Level:
100%
Response Time:
5,278ms
Service Level:
100%
Response Time:
5,299ms
Service Level:
100%
Response Time:
53ms
Service Level:
100%
Response Time:
55ms
Service Level:
100%
Response Time:
6,907ms
Service Level:
100%
Response Time:
609ms
Service Level:
100%
Response Time:
315ms
Service Level:
100%
Response Time:
257ms
Service Level:
100%
Response Time:
209ms
Service Level:
100%
Response Time:
169ms