Caching Content

Developers are encouraged to implement caching strategies, especially for static data such as metadata (e.g., the Books of the Bible for a particular translation).

Requirement: Refresh at least every 30 days

To comply with API.Bible's Terms & Conditions and IP holder restrictions, cached content must be refreshed at least once every 30 days. This is a contractual obligation. Cached content that exceeds 30 days without a refresh is considered non-compliant regardless of whether the content has changed.

Recommendation: Refresh every 14 days or less

We also recommend clearing your cache every 14 days or less. API.Bible is constantly improving and updating the structure of its data, and refreshing more frequently ensures those improvements reach your users sooner. This is a best-practice guideline, not a contractual requirement.

Content integrity

Modification of content from API.Bible and affiliated IP Holders is not permitted. The integrity of the Scriptures must be preserved in all forms of usage.

No change notifications

API.Bible does not send a notification when content data changes. There is currently no endpoint or metadata field for the last updated date of a content bundle. Developers should implement scheduled cache refreshes rather than relying on change-triggered invalidation.