Every developer needs a "throwaway" API at some point — for a tutorial, a demo, a button that does something on a portfolio site, or a quick exercise for learning a new language. This shortlist covers the fun APIs that have stayed reliably free and keyless for years.
Quick comparison
| API | Best for | Auth | Format |
|---|---|---|---|
| JokeAPI | Programming and category-filtered jokes | None | JSON or plain text |
| icanhazdadjoke | Dad jokes (single-purpose, polished) | None | JSON, plain, HTML |
| ChuckNorris.io | Random or search-filtered Chuck Norris jokes | None | JSON |
| Open Trivia DB | Quiz and trivia questions | None | JSON |
| Advice Slip API | Random or search-filtered advice | None | JSON |
| kanye.rest | Random Kanye West quotes | None | JSON |
What "fun" actually means here
For an API to qualify for this list:
- It must be free, keyless, and stable enough that the URL works the same way it did three years ago.
- It must serve content people actually want — jokes, quotes, trivia, advice — not just toy responses.
- It must be safe to embed in tutorials and demos without exposing anyone's data.
These APIs have all earned a spot in countless tutorials, classroom exercises, and "Hello World" demos for a reason.
API options
JokeAPI
JokeAPI is the most feature-rich joke API on this list. It supports categories (programming, dark, pun, miscellaneous, spooky, Christmas), multiple response formats, and content filters.
Use it when:
- You are teaching beginners and want category filters and content-flag handling.
- You want jokes appropriate for a specific audience (programming jokes for a dev tool demo).
- You need both single-line and two-part joke formats.
The integration is trivial: a single GET request, a clean JSON response.
icanhazdadjoke
icanhazdadjoke is the polished, single-purpose dad-joke API. It supports JSON, plain text, and HTML responses, with a User-Agent header recommended (not required) for attribution.
Use it when:
- Your demo is a dad-joke generator (more common than you'd think).
- You want a polished single-purpose API as a positive example for tutorials.
- You need plain text or HTML response formats, not just JSON.
ChuckNorris.io
ChuckNorris.io is a long-running joke API with random, category-filtered, and search-based endpoints. It is the API many tutorials reach for when "any joke API" will do.
Use it when:
- You want random JSON responses for test UIs.
- You need API health-check examples that always return predictable shapes.
- You want category and search endpoints in addition to random.
Open Trivia DB
Open Trivia DB is a community-maintained trivia database with parameterized JSON endpoints. It is the only API on this list designed for actual product use beyond demos.
Use it when:
- You are building a quiz or trivia game.
- You need category and difficulty filtering.
- You want multiple-choice or true/false question types.
The API includes a token system to avoid serving duplicate questions in a session — helpful for real quiz UX.
Advice Slip API
Advice Slip API returns random advice "slips" or supports search by keyword. It is small, focused, and reliably keyless.
Use it when:
- Your demo is a "daily advice" widget.
- You want a small JSON shape for tutorial code that fits on one screen.
- You need both random and search endpoints.
kanye.rest
kanye.rest returns random Kanye West quotes. That's the entire API, and it's been steady for years.
Use it when:
- You need the simplest possible API for a tutorial — one endpoint, one field in the response.
- You are building a portfolio demo and want a one-line API call.
- The vibe matches your project.
Picking the right one
Match the API to the demo:
- Programming or dev-tool demo → JokeAPI (use the programming category).
- Polished single-purpose example → icanhazdadjoke.
- Quick random JSON for any test UI → ChuckNorris.io.
- Quiz or trivia product → Open Trivia DB.
- Tutorial about API responses with a small JSON shape → Advice Slip or kanye.rest.
For real products, only Open Trivia DB is built for production use. The rest are best for demos, tutorials, and learning exercises.
When not to use these APIs
These APIs are great for what they are, but they are not the right fit when you need:
- Production traffic at scale. They are public and free. Cache aggressively and don't hammer them.
- Custom or branded content. They serve their own datasets. For a real product, you usually want your own content layer.
- Content moderation guarantees. "Programming jokes" are mostly safe; some other categories are not. Filter on the client.
Related API Deposu entries
Sources
Frequently Asked Questions
›Which fun API is the best for learning HTTP requests?
JokeAPI is the most well-documented option with category filters, multiple response formats, and good error handling — ideal for teaching beginners about HTTP, query parameters, and JSON parsing.
›Are these APIs really free with no sign-up?
Yes — all six APIs in this list work without any account or API key. They are designed for public use, demos, and tutorials.
›Can I build a quiz game with one of these?
Open Trivia DB is purpose-built for quiz games. It supports filtering by category, difficulty, and question type, and returns questions in clean JSON format.
›Are there usage limits I should know about?
These APIs are generous but not infinite. Add caching, avoid hammering them in tight loops, and respect any rate-limit headers — common courtesy keeps the public APIs free for everyone.