The Cathopic API allows you to integrate Catholic visual content directly into your application, website, or platform. However, API usage is strictly governed by our API License Agreement, which limits use to specific digital environments.
What you can build
Church and parish management systems
Allow parishes to add Catholic imagery to their bulletins and newsletters
Enable event promotion with relevant visual content
Provide liturgical images that match the church calendar
Create digital displays for parish announcements
Catholic content platforms
Build blogging platforms for Catholic writers with integrated imagery
Create Catholic news websites with relevant visuals
Develop devotional apps with daily images and prayers
Design catechetical platforms with visual teaching aids
Email marketing tools
Allow ministries to create newsletters with Catholic imagery
Enable religious organizations to design email campaigns
Provide templates with integrated Cathopic content
Support fundraising campaigns with appropriate visuals
Website builders and CMS
Integrate Catholic imagery into website building platforms
Provide content modules for Catholic organizations
Enable drag-and-drop image selection from Cathopic
Create templates specifically for Catholic ministries
Event and social media management
Help ministries create social media graphics (without downloading files)
Design event invitation systems with Catholic imagery
Build content calendars with liturgical season visuals
Enable organizations to schedule posts with appropriate images
Critical restrictions you must follow
The API License strictly prohibits certain uses. Violating these restrictions may result in immediate termination:
❌ AI/ML training (PERMANENTLY PROHIBITED)
Cannot be used to train, fine-tune, or feed any AI/ML models
Cannot create embeddings, datasets, or derivative extracts for AI
This restriction survives indefinitely, even after agreement termination
Applies to all forms of machine learning and artificial intelligence
❌ File downloads and exports
End users cannot download or save content as files
Cannot provide "download" or "export" functionality
Content must remain hosted by Cathopic or in authorized cache
Only web-optimized URLs can be used, not original files
❌ Print and offline use
Cannot be used in print materials, brochures, or posters
No offline advertising or physical products
Strictly limited to digital web and email environments
Cannot be incorporated into PDFs meant for printing
❌ Resale and redistribution
Cannot create products that resell or redistribute Cathopic content
Cannot build stock photo marketplaces using our API
Cannot offer content as a standalone product
Must be integrated as part of a larger service
❌ Modification and derivatives
Cannot alter, transform, or create derivative works
Cannot apply filters or significant modifications
Must display content as provided by the API
Basic cropping and resizing are permitted for layout purposes
Only web and email environments
Content accessed through the API can only be used in:
Websites: Public or private web pages
Web applications: Browser-based tools and platforms
Email: Newsletters, campaigns, and transactional emails
Blogs: Online content management systems
Web embeds: Controlled iframe or API-served content
Important: Content must be displayed at web-optimized resolution only. Original high-resolution files are never accessible through the API.
Technical requirements
Your application must:
Use HTTPS: All API calls and content delivery must be secure
Implement watermark handling: Start with watermarked content, request unwatermarked only when needed
Track usage accurately: Log all content usage for billing purposes
Call /confirm endpoint: When end user commits to using content
Call /remove endpoint: When content is no longer in use (stops billing)
Prevent unauthorized access: Protect your API credentials
Respect rate limits: Follow the limits set for your account
Your legal obligations
When you integrate the API, you must:
Update your Terms of Use to inform end users:
Content cannot be downloaded or used outside your application
Content cannot be used for AI/ML purposes
Content is owned by Cathopic and its creators
Usage is tracked for billing and compliance
Implement technical controls to prevent:
Right-click downloads (where feasible)
Direct URL access to original files
Browser extensions that enable downloads
Maintain usage logs for:
Billing verification
Compliance audits
Dispute resolution
Examples of compliant integrations
✅ Parish bulletin builder
Parishes create digital bulletins with Catholic images
Content displays on website and in email newsletters
No download functionality provided
Billing tracks usage per parish and per image
✅ Ministry email platform
Religious organizations design email campaigns
Images served directly in emails via API URLs
Billed per email sent with content
No file storage on end user devices
✅ Catholic CMS platform
Website builder with integrated Cathopic library
Users browse and select images for their pages
Content embeds via API-served URLs
Billed per day of use per user
Examples of prohibited integrations
❌ AI-powered image generator
Using Cathopic content to train AI models
Creating datasets for machine learning
Generating similar images based on our content
❌ Print design tool
Allowing users to create printable posters
Providing download for high-res printing
Creating PDFs with Cathopic content for print
❌ Stock photo marketplace
Reselling Cathopic content as standalone products
Creating derivative stock photo collections
Redistributing content to multiple clients
Before you start building
Essential reading:
Review the complete API License Agreement
Study the technical documentation at api.cathopic.com/docs
Understand the billing model in detail (see How is API usage billed?)
Plan your integration to comply with all restrictions
Contact us via support if you have questions
Remember: By accessing or using the API, you accept all terms in the API License Agreement. Non-compliance may result in immediate termination and legal consequences.
