Email admin@kookee.dev.
Bugs, billing questions, account problems, or anything the documentation did not answer — that address reaches the team.
Before you write
A quick check that resolves a good share of reports:
Empty results or a missing article — work through Why is my content not showing up? The usual causes are draft status, a stale cache and locale filters.
A 401 or 403 — see Authentication and permission errors. Most of these are an environment variable that did not load.
Escaped HTML or unstyled code blocks — see Content renders wrong or unstyled. Usually a missing stylesheet import.
What to include
The difference between a one-reply fix and a three-day thread is usually detail. Helpful things to send:
What you expected and what happened instead, concretely — "the list returns 0 items" beats "the blog is broken"
The project slug so we can find your content
The exact error, including
codeandstatusfrom aKookeeApiErrorThe failing call, with parameters
Whether the same request works with
curl, which separates an application problem from an API one:
curl -i -H "Kookee-API-Key: YOUR_API_KEY" \
"https://api.kookee.dev/v1/blog/posts?limit=5"Never send an API key. Not in an email, a screenshot or a log paste. We never need it, and we will never ask for it — anyone who does is not us. If a key has appeared somewhere it should not, revoke it on Connect → API keys (or Connect → MCP server for an MCP token) and create a replacement.
Bugs and feature requests
Reproducible bugs and feature ideas are welcome by email, and also on the public feedback board where other users can vote and comment. Posting there means your request is visible on the roadmap as its status changes, rather than living in a private thread.
Security issues should go to admin@kookee.dev directly rather than the public board — please do not open a public post for a vulnerability.
What to expect
We read everything. Include the details above and the first reply is far more likely to be an answer than a request for more information.