Our API is a RESTful service that lets you integrate Cathopic's Catholic media library directly into your applications. Access thousands of images, videos, and graphics programmatically.
What you can do
Search and browse through our complete catalog
License resources for your end-users automatically
Download in multiple formats optimized for different use cases
Access rich metadata including tags, descriptions, and liturgical information
REST architecture
Built on standard REST principles:
Base URL:
https://api.cathopic.comData format: JSON requests and responses
Authentication: API key via
x-api-keyheaderHTTP method: POST for all endpoints
Four core endpoints
POST /resources - Search the catalog
POST /resource - Get details about a specific item
POST /confirm - License a resource and get download URLs
POST /remove - Stop licensing when no longer needed (website only)
Complete documentation
Everything you need is available online:
Interactive API reference: api.cathopic.com/docs
Code examples in multiple languages
Detailed parameter specifications
Getting started
Contact our team to request API access
Generate your API key in Settings → API
Add a payment method for usage billing
Start building
Check out the other questions in this section for details on authentication, billing, and best practices.
API License Agreement
All API usage is subject to our API License Agreement. Key points to understand:
Digital use only: Content can only be displayed in web and email environments
No file downloads: End users cannot download or export original files
Prohibited uses: AI/ML training, print materials, and offline use are strictly forbidden
Usage-based billing: Pay only for actual content usage by your end users
By using the API, you accept all terms in the license agreement
Before integrating the API:
Review the complete API License Agreement
Understand the restrictions and obligations
Ensure your use case complies with digital-only requirements
Plan your integration to track usage accurately for billing
For more details, see:
What can I build with the API? (includes detailed restrictions)
How do licenses work via API? (complete licensing details)
How is API usage billed? (billing model explanation)
