# 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:
1. Word definitions
2. Strong's numbers for the word
3. Greek/Hebrew translations

## What We Need

Look for these endpoints in the RapidAPI playground:

1. **Word Definition Endpoint** - Something like:
   - `/word/{word}` or `/words/{word}`
   - `/definition/{word}`
   - `/lookup/{word}`

2. **Word to Strong's Conversion** - Something like:
   - `/word-to-strongs/{word}`
   - `/search-word/{word}` (returns Strong's numbers)

3. **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

1. **Check the RapidAPI playground** for other endpoints
2. Look for endpoints that:
   - Take a word as input
   - Return definitions, Strong's numbers, or Greek/Hebrew
3. Share any other endpoints you find

## Testing

Once you find a word definition endpoint, test it:

```javascript
// Test the endpoint you found
await window.testRapidAPICustomEndpoint('/your-endpoint-here/{word}', 'love');
```

The integration will automatically try to parse whatever the API returns!