FaithGPT API for Developers

Current Status: API access is available for approved partners and enterprise customers. Contact us to discuss your integration needs.

Base URL: https://api.faithgpt.io/v1

Authentication: Bearer token authentication required for all endpoints.

Rate Limits: Vary by plan. Standard: 100 requests/minute. Enterprise: Custom limits.

Response Format: JSON for all endpoints.

Scripture Insights

• POST /insights - Get AI-powered insights for a passage
• Parameters: passage (string), translation (optional)

Verse Search

• POST /verses/search - Semantic search for verses by topic
• Parameters: query (string), limit (integer, default 10)

Theology Q&A

• POST /theology/ask - Ask theological questions
• Parameters: question (string), context (optional)

Prayer Generation

• POST /prayer/generate - Generate prayers from prompts
• Parameters: topic (string), style (optional)

Obtaining API Keys

1. Apply for API access at faithgpt.io/api-access
2. Receive API key via email after approval
3. Include in all requests as Bearer token

Example Request

curl -X POST https://api.faithgpt.io/v1/insights \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"passage": "John 3:16"}'

Security: Never expose API keys in client-side code. Use server-side proxies.

Church Apps: Add Scripture insights to your church's mobile app.

Bible Study Platforms: Integrate AI explanations alongside Scripture text.

Prayer Apps: Generate personalized prayers based on user situations.

Christian Education: Provide AI tutoring for Bible courses.

Devotional Content: Auto-generate daily devotional insights.

Sermon Tools: Assist pastors with passage research and illustrations.

Step 1: Apply for API access

• Visit faithgpt.io/api-access
• Describe your use case and expected volume
• Our team will review within 2-3 business days

Step 2: Integration planning

• Review rate limits for your plan
• Plan error handling for quota exceeded
• Consider caching for common queries

Step 3: Development

• Use sandbox environment for testing
• Implement proper error handling
• Test edge cases before production

Step 4: Launch

• Move to production environment
• Monitor usage and adjust as needed