kagiapi Python: passing cache=True gives 500 Internal Server Error

TL;DR

For "kagiapi Python: passing cache=True gives 500 Internal Server Error": what actually fixes it (verified in the thread): 3. PR #5 (merged the same day) fixed it by lowercasing the cache parameter so it goes out as true/false. Workaround if you are on an older checkout: pass the cache value as a lowercase string yourself, or upgrade to a version containing PR #5.

kagiapi Python: passing cache=True gives 500 Internal Server Error

When to use

You are seeing this: Using the kagiapi Python package from main against the Kagi Search API, every request passed with cache=True consistently returned a 500 Internal Server Error. Use this skill when you run into "kagiapi Python: passing cache=True gives 500 Internal Server Error".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Steps

1. Using the kagiapi Python package from main against the Kagi Search API, every request passed with cache=True consistently returned a 500 Internal Server Error. The other search parameters worked, so the reporter suspected the cache flag handling specifically.
2. What actually fixes it (verified in the thread):
3. The bug was in how the package serialized the flag: it sent the GET parameter capitalized as True/False, which the Kagi API rejects with a 500. PR #5 (merged the same day) fixed it by lowercasing the cache parameter so it goes out as true/false. Workaround if you are on an older checkout: pass the cache value as a lowercase string yourself, or upgrade to a version containing PR #5.

Someone asked: Using the kagiapi Python package from main against the Kagi Search API, every request passed with cache=True consistently returned a 500 Internal Server Error. The other search parameters worked, so the reporter suspected the cache flag handling specifically. The verified answer: The bug was in how the package serialized the flag: it sent the GET parameter capitalized as True/False, which the Kagi API rejects with a 500. PR #5 (merged the same day) fixed it by lowercasing the cache parameter so it goes out as true/false. Workaround if you are on an older checkout: pass the cache value as a lowercase string yourself, or upgrade to a version containing PR #5. Full thread: https://vectle.com/threads/thrL1QsEBNklHtI_IHrrqx4A