How to Find Copyright and Public Domain Status of Bibles

When building an application or website using API.Bible, understanding the copyright status of Bible translations is essential for legal compliance and proper attribution. Bible versions on API.Bible fall into two broad categories: Open Access (which includes Public Domain and Creative Commons translations) and Licensed (which includes Standard License and Unique License translations).

Knowing where a translation sits determines what you can build, whether you need a paid plan, and what attribution you must display.

1. Understanding Copyright Status Categories

Open Access

• Public Domain — Older translations such as the King James Version whose copyright has expired. These carry the fewest restrictions and are available on all plans, including the free Starter plan.
• Creative Commons — Translations licensed for broader use, but which may require specific attribution or share-alike terms (e.g. CC-BY or CC-BY-SA). Available on all plans. Important: Not all Creative Commons licenses permit commercial use. For example, a CC-NC (Non-Commercial) translation cannot be used in a revenue-generating app. Always verify the specific CC license terms for each translation before use.

Licensed

• Standard License — Modern translations such as the NIV or NASB that are protected by copyright. These require proper attribution and may require a paid plan depending on your use case.
• Unique License — Some translations require a separate agreement directly with the publisher before they can be activated on your API key.

2. How to Check a Bible's Copyright Status

Option A: The Bibles Page (recommended for most users)

Browse and filter all available translations at: api.bible/bibles

1. Log in to your account
2. Use the License filter to sort translations by: Open Access, Standard License, or Unique License
3. Each listing shows the translation name, publisher/organization, language, and license type

Option B: The API Endpoint (for developers)

Query the GET /bibles/{bibleId} endpoint to retrieve copyright metadata programmatically. In the JSON response, look for the copyright field, which contains the exact attribution text required for display in your application.

You can browse, test, and generate code snippets for this endpoint — in Shell, Ruby, Node.js, PHP, Python and more — using the interactive API reference at api.bible/api-reference. You'll need your API key to authenticate. The reference also includes GET /bibles, which lists all available Bibles and their metadata, useful for checking license status across your full set of translations at once.

3. What Copyright Status Means for Your App

Important: The Starter (free) plan is strictly non-commercial — it does not permit ads, fees, freemium models, upsells, or any other revenue-generating use, regardless of which translations you use. For full details on commercial use licensing, see Express Licensing for Commercial Use.

4. Attribution Requirements

Attribution is required for all content accessed via API.Bible, with the exception of content that is explicitly labeled as Public Domain.

Getting your attribution text

Use the Citations tool in your API.Bible application dashboard to get correct, publisher-approved attribution text for your translations. You'll find it at the bottom of the dashboard.

The tool covers both license types — Licensed and/or Copyright Reserved, and Creative Commons and Public Domain. For the most popular translations, pre-made citations are ready immediately. Find your translation in the list, click Copy, and choose your preferred format:

• Copy Text — plain text, for example: Amplified® Bible, Copyright © 2015, The Lockman Foundation. All rights reserved. lockman.org
• Copy HTML — ready to paste directly into your web app
• Copy CSS — for styled implementations

Use the text exactly as provided. Do not paraphrase, reformat, or abbreviate it unless you are in a space-constrained context, in which case refer to the short-form guidance in the API.Bible Terms & Conditions.

For programmatic retrieval, attribution text is also available via the copyright field in the /bibles/{bibleId} API endpoint.

Starter vs. Pro plan attribution

• Starter Plan users must include a visible citation and hyperlink to https://api.bible within their application's interface.
• Pro Plan users are encouraged, but not required, to provide this attribution.

FUMS (Fair Use Management System)

Web applications must implement FUMS wherever Scripture is rendered. For full details, see Understanding FUMS.

5. Frequently Asked Questions

Can I use Public Domain Bibles for free?

Yes. Public Domain and Creative Commons translations are available on all plans including the free Starter plan, subject to their respective license terms.

Can I use Creative Commons Bibles commercially?

It depends on the specific CC license. Some Creative Commons licenses prohibit commercial use (e.g. CC-NC). Always verify the license terms for each translation before using it in a revenue-generating app. License details are available in each translation's metadata via the API.

Where do I find the attribution text I need to display?

Use the Citations tool in your application dashboard. It provides pre-made, publisher-approved attribution text in plain text, HTML, and CSS formats for the most popular translations. For programmatic access, attribution text is also available via the copyright field in the /bibles/{bibleId} endpoint.

How do I get access to a translation that appears locked?

Translations may be locked because they require a paid plan (Standard License) or a direct agreement with the publisher (Unique License). Contact support@api.bible for assistance.

Can I modify the text of a copyrighted Bible?

No. Scripture text must not be altered, as modifications may violate publisher licensing agreements and API.Bible's Terms and Conditions.