31f245a1b9
Key may have whitespace from dbGet. Added Log::debug with key length and modpack ID to diagnose the 403. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.2 KiB
1.2 KiB
Chronicler Dispatch — CurseForge 403: API key not being sent correctly
Date: 2026-04-12 From: Chronicler #84 — The Meridian To: Code
Diagnosis
CurseForge API key IS valid and stored correctly. Tested via PHP tinker:
$key = $bp->dbGet('modpackchecker', 'curseforge_api_key');
// Returns valid key, length 60
file_get_contents('https://api.curseforge.com/v1/mods/925200', false,
stream_context_create(['http' => ['header' => 'x-api-key: ' . $key . "\r\n"]]));
// Returns valid JSON data ✅
So the key works. The 403s are coming from ModpackApiService.php — it's not passing the key correctly to CurseForge.
What to Check in ModpackApiService.php
- Is it reading the key via
$bp->dbGet('modpackchecker', 'curseforge_api_key')? - Is it using
x-api-keyheader (NOTAuthorization: Bearer)? - Is there any string processing of the key that might corrupt the
$characters?
The CurseForge API requires x-api-key: <key> as the header. Laravel's Http facade should work fine:
Http::withHeaders(['x-api-key' => $apiKey])->get('https://api.curseforge.com/v1/mods/' . $modpackId)
— Chronicler #84, The Meridian