Support#

Single human (the founder, Maciej Dzierżek) reads every report. Response within 48 hours on weekdays (Europe/Warsaw).

Where to report what#

Issue type	Where
API bug, broken endpoint, regression (logged in)	Dashboard header → “Report a problem” button. Pre-fills `endpoint`, `request_id`, `user_tier`, Sentry breadcrumbs.
Hit an error page (500, 404)	Same button is on every error page — adds the failing Sentry event ID.
API bug (not logged in)	Page footer → “Report a bug” opens a `mailto:` draft. Include `X-Request-Id` from response headers.
TypeScript SDK bug (types, retry, error mapping)	github.com/maciejdzierzek/quizbase-sdk-ts/issues
Content bug in a question (wrong answer, bad translation)	`POST /api/v1/report` (public, no key — see below) or the `quizbase_report` MCP tool
Security vulnerability	security.txt — do NOT open a public issue or use the report button
Business, partnerships, press	[email protected]

How to file a bug#

Find the request ID. Every API response carries X-Request-Id in the headers and meta.requestId in the JSON body — log it on every non-2xx response.
Open the “Report a problem” button — top of the dashboard, or right on the error page if you hit one.
Pick the type — Bug (most common), Feature request, or Question.
Describe expected vs actual + steps to reproduce. Optionally leave your email if you want a reply. We will not auto-email you otherwise.

Reporting a problem with a question content#

Wrong answer, translation that distorts meaning, inappropriate question, missing/incorrect attribution? Use POST /api/v1/report — public, no API key required, rate-limited 5/min/IP.

curl -X POST https://quizbase.runriva.com/api/v1/report 
  -H "Content-Type: application/json" 
  -d '{
    "questionId": "019db549-b3ff-7228-9174-3dfc7bf30415",
    "type": "translation",
    "comment": "Polish translation reverses the meaning",
    "reporterEmail": "[email protected]"
  }'

type is one of translation, factual, inappropriate, attribution, other. reporterEmail is optional but lets us follow up. See POST /v1/report for full details.

This is also the channel for translation correction requests under Polish Pr.Aut. Art. 16(3) (moral rights).

Not support-worthy — check these first#

401 Unauthorized — check your key prefix (test vs live) and X-API-Key header
429 Too Many Requests — read Errors and retries; wait Retry-After seconds
Empty data: [] — your filters matched no rows; broaden them
“Why is this question translated this way?” — translator is attribution.translator; for community models, report to the upstream source listed in attribution.url

What we do with your report#

The dashboard button uses Sentry’s User Feedback Widget — your comment is attached to a Sentry event (which carries the stack trace, request ID, and breadcrumbs we already collected). Privacy: see § 6 of our Privacy Policy — Sentry is a listed sub-processor.

Community#

Discord — on the post-launch roadmap. Watch the changelog for the announcement.