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, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests_per_minute.

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 Throttle: 429
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