4Chan Rate Limits
4chan publishes hard client-side rate-limit rules in the API README that all clients MUST observe. The limits are per-client (enforced by IP at the network edge) and apply uniformly regardless of who is calling — there is no per-account scoping because there is no authentication. Two rules dominate: no more than one request per second across all endpoints, and any per-thread polling loop must wait at least 10 seconds (preferably longer) between requests against `/{board}/thread/{thread}.json`. Clients SHOULD also send `If-Modified-Since` so unchanged threads are served as `304 Not Modified` and do not count against an effective fetch budget.
4Chan Rate Limits is the machine-readable rate-limit profile for 4chan on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions, measuring requests_per_second, requests_per_minute, and varies.
Limit state is signalled in the ifModifiedSince and lastModified response headers, and an exhausted limit returns HTTP 503.
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 notModified, notFound, and throttled.
Tagged areas include Rate Limiting, Social, Imageboard, and Read Only.
ifModifiedSincelastModified
generated, dated 2026-05-28.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.