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>
2.1 KiB
2.1 KiB
How to Find the Correct RapidAPI Endpoint
Step 1: Go to RapidAPI Playground
Step 2: Find the Endpoint
- Look at the left sidebar - you'll see different endpoints listed
- Click on endpoints that look like they might search for words (e.g., "Search Word", "Get Word", "Word Definition")
- Look at the endpoint URL shown - it will be something like:
/api/word/{word}/words/search/search/word- etc.
Step 3: Test It
- Enter a test word (like "love") in the parameters
- Click "Test Endpoint"
- If it works, you'll see the response data
Step 4: Copy the Endpoint Path
Copy the exact endpoint path (the part after the domain). For example:
- If the full URL is:
https://complete-study-bible.p.rapidapi.com/api/word/love - The endpoint path is:
/api/word/{word}or/api/word/love(replacelovewith{word})
Step 5: Test It in Your App
Once you have the endpoint, test it:
// Example: if the endpoint is /api/word/{word}
await window.testRapidAPICustomEndpoint('/api/word/{word}', 'love');
// Or if it's /words/search?word=love
await window.testRapidAPICustomEndpoint('/words/search?word={word}', 'love');
Step 6: Update the Code
Once you find a working endpoint, tell me what it is and I'll update rapidapi-study-bible.js to use it!
Common Endpoint Patterns
RapidAPI APIs often use:
/api/{resource}/{id}- RESTful pattern/api/{resource}/search- Search pattern/api/search?q={query}- Query parameter pattern/v1/{resource}/{id}- Versioned API pattern
Look for endpoints that mention:
- "word"
- "search"
- "definition"
- "lookup"
- "find"
Still Can't Find It?
- Check the API documentation tab on RapidAPI
- Look at the "Endpoints" section
- Try clicking through different endpoints to see what they do
- The endpoint name/description usually gives hints about what it does