Exploring our Public API

Getting Started with the DBL Public API

The DBL Public API (Application Programming Interface) allows third-party applications to interact directly with the Digital Bible Library. It provides authorized access to key content and licensing data and enables streamlined workflows like downloading files or uploading content.

Whether you're a developer integrating DBL into your platform, or a partner curious about what the API offers, this guide gives you a clear starting point.

Overview for Partners and Project Managers

The Public API gives your team access to:

  • Bible content metadata – Search and browse available resources
  • License agreements and templates – View and manage agreements
  • Download functionality – Pull content you’re licensed to use
  • Upload capability – Submit new Bible content (if you have permission)

To use the API, your organization must have:

  • A DBL account
  • The appropriate permissions (e.g., Content Manager role)
  • A basic understanding of what data you need to access

If you're not a developer, simply speak with your technical team about how the API can support your workflows.

Developer Quick Start

For developers, the Public API supports the following core endpoints:

  • `GET /items` – List content items
  • `GET /items/{id}/files` – Download licensed files
  • `GET /licenses` – Retrieve license agreements
  • `GET /license-templates` – View license templates
  • `POST /items` – Upload new content items

Authentication

Access requires an API token issued by DBL. Tokens are tied to your user role and organization.

Example: List Content Items

curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

https://api.digitalbiblelibrary.org/v1/items

Documentation and Next Steps

For full technical details—including response schemas, query parameters, and example workflows—visit our official API documentation: Public API Documentation

If you're unsure whether API access is right for your team, feel free to reach out to support@library.bible for guidance.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.