quizbase
Skip to content
Command Palette
Search for a command to run...
QuizBase · Docs

Quickstart#

From signup to your first response in five steps. Total time: about 5 minutes.

1. Sign up#

Create a free account — no credit card required. The Free tier gives you the full API: every endpoint, the entire 1.2M+ catalog, English and Polish, 500 requests/day, 10 burst/10s.

2. Generate your API key#

In the dashboard, open API keys and click Create key. Pick qb_pk_* for browser/mobile code (CORS-enabled) or qb_sk_* for server-side. Both share the same per-user quota.

3. Make your first request#

Pick your language. The key placeholder below is auto-filled once you sign in.

Sign in to pre-fill your API key 
curl -H "X-API-Key: qb_pk_YOUR_KEY_HERE" \
     "https://quizbase.runriva.com/api/v1/questions/random?amount=1&lang=pl"

4. Inspect the response#

Every question ships with attribution — license, author, source. Keep these in your cache layer; the CC-BY-SA chain requires them.

Use the TypeScript SDK#

If you’re on Node, Deno, Bun, or in a browser — skip the raw fetch and install the official typed client:

pnpm add @quizbase/client
import { createClient } from '@quizbase/client';

const client = createClient({ apiKey: process.env.QUIZBASE_API_KEY! });
const random = await client.questions.random({ amount: 5, lang: 'pl' });
console.log(random.data);

Typed responses, automatic retry on 429 / 5xx, RFC 9457 typed errors, and an onRequest telemetry hook out of the box. Full reference: /docs/sdks/typescript.

What to expect — performance#

The catalog is 1.2M+ approved questions, served from a high-performance cache layer behind a global CDN. Single-request warm: discovery endpoints respond in ~25-60ms; /v1/questions and /v1/questions/:id around 80-110ms; /v1/questions/random around 130ms. Under sustained 50 RPS load: p95 ranges ~45ms (discovery) to ~265ms (random), ~0.01% errors. SLO: p95 < 500ms, error rate < 1%.

Full numbers, methodology, and quarterly drift mechanism: /docs/performance. Each /docs/api/* page also lists a per-endpoint Performance section.

5. Next steps#