Listmonk Rate Limits
As a self-hosted application, listmonk does not impose a vendor-side API rate limit; throughput is bounded only by the operator's own server, PostgreSQL database, and configuration. The relevant throttles are operator-controlled message-sending concurrency and per-messenger sliding windows configured in Settings (number of concurrent workers, messages per second), plus any rate limits imposed by the downstream SMTP / email provider used for outbound delivery. Specific numeric values depend entirely on the operator's deployment and are not fixed by the project.
Listmonk Rate Limits is the machine-readable rate-limit profile for listmonk on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring requests, workers, and messages.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Email, Newsletter, Mailing List, Open Source, and Self-Hosted.
Limits
Policies
Sources
- https://listmonk.app/docs/apis/apis/
- https://listmonk.app/docs/maintenance/performance/
- https://github.com/knadh/listmonk
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/listmonk-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.