npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

free-use-bible-api

v0.2.0

Published

Access over 1000 Bible translations in over 700 languages for free

Downloads

326

Readme

Free Use Bible API

TypeScript and JavaScript client for the public Free Use Bible API:

  • https://bible.helloao.org

Installation

npm install free-use-bible-api
pnpm add free-use-bible-api
yarn add free-use-bible-api

Quick Start

import { FreeUseBibleApi } from 'free-use-bible-api';

const api = new FreeUseBibleApi();

const available = await api.getAvailableTranslations();
console.log('Total translations:', available.translations.length);

const books = await api.getTranslationBooks('BSB');
console.log('Books in BSB:', books.books.length);

const chapter = await api.getTranslationBookChapter('BSB', 'GEN', 1);
console.log('Verses in Genesis 1:', chapter.numberOfVerses);

Client Options

You can customize the client with FreeUseBibleApiOptions:

import { FreeUseBibleApi } from 'free-use-bible-api';

const api = new FreeUseBibleApi({
    endpoint: 'https://bible.helloao.org/',
    useCache: true,
});
  • endpoint: Base API endpoint.
  • useCache: Enables in-memory response caching (default: true).

API Methods

Translations

  • getAvailableTranslations(endpoint?)
  • getTranslationBooks(translation, endpoint?)
  • getTranslationBookChapter(translation, book, chapter, endpoint?)
  • getCompleteTranslation(translation, endpoint?)

getCompleteTranslation() disables per-request cache internally because payloads are typically large.

Commentaries

  • getAvailableCommentaries(endpoint?)
  • getCommentaryBooks(commentary, endpoint?)
  • getCommentaryBookChapter(commentary, book, chapter, endpoint?)

Datasets

  • getAvailableDatasets(endpoint?)
  • getDatasetBooks(dataset, endpoint?)
  • getDatasetBookChapter(dataset, book, chapter, endpoint?)

Chapter Navigation Helpers

  • getNextChapter(chapter, endpoint?)
  • getPreviousChapter(chapter, endpoint?)

These helpers work with translation, commentary, and dataset chapter responses.

Examples

Get a complete translation

const complete = await api.getCompleteTranslation('BSB');
console.log(complete.translation.id);
console.log(complete.books.length);

Read a commentary chapter

const comm = await api.getCommentaryBookChapter('matthew_henry', 'GEN', 1);
console.log(comm.book.name);

Read a dataset chapter

const dataChapter = await api.getDatasetBookChapter(
    'cross_references',
    'JHN',
    3
);
console.log(dataChapter.book.name);

Navigate to next/previous chapter

const current = await api.getTranslationBookChapter('BSB', 'GEN', 1);

const next = await api.getNextChapter(current);
const previous = await api.getPreviousChapter(current);

console.log(next?.chapter.number);
console.log(previous?.chapter.number);

Direct HTTP Endpoints

Translation endpoints

  • GET /api/available_translations.json
  • GET /api/{translation}/books.json
  • GET /api/{translation}/{book}/{chapter}.json
  • GET /api/{translation}/complete.json

Commentary endpoints

  • GET /api/available_commentaries.json
  • GET /api/{commentary}/books.json
  • GET /api/{commentary}/{book}/{chapter}.json

Dataset endpoints

  • GET /api/available_datasets.json
  • GET /api/d/{dataset}/books.json
  • GET /api/d/{dataset}/{book}/{chapter}.json

Example requests:

curl https://bible.helloao.org/api/available_translations.json
curl https://bible.helloao.org/api/BSB/books.json
curl https://bible.helloao.org/api/BSB/GEN/1.json
curl https://bible.helloao.org/api/available_commentaries.json
curl https://bible.helloao.org/api/available_datasets.json

Error Handling

Methods throw on non-2xx responses.

A 404 response usually means one of the path values is invalid, for example:

  • translation
  • commentary
  • dataset
  • book
  • chapter

Notes

  • Uses the global fetch API.
  • For Node.js, use a runtime that provides fetch (Node 18+ recommended) or polyfill it.