christianandClaude Opus 5
0db5e9b07d
First commit on the local Gitea server, made after moving the tree off the Windows machine. Build outputs, node_modules and the AI models stay out (see .gitignore); everything the installer build needs is tracked. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1.7 KiB
1.7 KiB
RapidAPI Endpoint Information
Found Endpoint
You found: /search-strongs/{strongs}/{bool}/
Example:
GET https://complete-study-bible.p.rapidapi.com/search-strongs/G4931/true/
Response: Returns an array of Bible verses containing that Strong's number.
Problem
This endpoint searches by Strong's number, not by word. For word popups, we need:
- Word definitions
- Strong's numbers for the word
- Greek/Hebrew translations
What We Need
Look for these endpoints in the RapidAPI playground:
-
Word Definition Endpoint - Something like:
/word/{word}or/words/{word}/definition/{word}/lookup/{word}
-
Word to Strong's Conversion - Something like:
/word-to-strongs/{word}/search-word/{word}(returns Strong's numbers)
-
Strong's Definition - Something like:
/strongs/{strongs}/definition/strongs/{strongs}/info
Current Status
The /search-strongs/ endpoint gives us:
- ✅ Cross-references (verses where the word appears)
- ✅ Usage count
- ❌ Word definitions
- ❌ Greek/Hebrew text
- ❌ Strong's number (unless we already have it)
Next Steps
- Check the RapidAPI playground for other endpoints
- Look for endpoints that:
- Take a word as input
- Return definitions, Strong's numbers, or Greek/Hebrew
- Share any other endpoints you find
Testing
Once you find a word definition endpoint, test it:
// Test the endpoint you found
await window.testRapidAPICustomEndpoint('/your-endpoint-here/{word}', 'love');
The integration will automatically try to parse whatever the API returns!