JokeAPI · Rate Limits

Jokeapi Rate Limits

JokeAPI enforces rate limits per IP address (no API keys, no accounts). Standard endpoints allow 120 requests per minute per IP. The /submit endpoint has a stricter 5-per-minute ceiling to discourage spammed submissions. Limits are hard — there is no paid raise — but operators can self-host the open-source codebase to remove them entirely.

Jokeapi Rate Limits is the machine-readable rate-limit profile for JokeAPI on the APIs.io network, in the API Commons Rate Limits shape.

It captures 2 rate-limit definitions, measuring requests_per_minute.

Limit state is signalled in the retryAfter, rateLimitLimit, rateLimitRemaining, and rateLimitReset response headers, and an exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 5 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Rate Limiting, Jokes, Humor, and Open Source.

2 Limits Exhausted: HTTP 429 retryAfterrateLimitLimitrateLimitRemainingrateLimitReset
Method: generated, dated 2026-05-29.
Written by API Evangelist on 2026-05-29 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Rate LimitingJokesHumorOpen Source

Limits

Standard endpoints IP
requests_per_minute · minute
120
Applies to /joke/{category} and every read endpoint (/categories, /flags, /formats, /languages, /langcode/{language}, /info, /endpoints, /ping). Counter is per requesting IP.
Joke submissions IP
requests_per_minute · minute
5
Applies to POST /submit. Stricter ceiling to discourage spam. Honoured even when ?dry-run is set.

Policies

No API keys
There are no API keys or accounts. Rate limits are enforced on the requesting IP address. CDN-fronted clients (especially mobile and shared NAT environments) may share a single budget.
Honour Retry-After
On a 429 response, clients SHOULD wait the number of seconds indicated by the Retry-After header before retrying. The RateLimit-Reset header reports the absolute reset timestamp.
Backoff on 429
Implement exponential backoff with jitter when retrying after a 429. Do not hot-loop — the burst budget is small and shared.
Self-host to remove limits
Operators with high-volume needs can clone the MIT-licensed source from git.sv443.net (mirrored on GitHub) and host their own instance with whatever (or no) rate limit applied.
CORS-friendly
CORS is enabled so browser clients can call the API directly. Be aware that browser-side calls hit the user's IP budget.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/jokeapi-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.