listmonk · Rate Limits

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.

4 Limits Throttle: 429
EmailNewsletterMailing ListOpen SourceSelf-HostedRate LimitingQuotasThrottling

Limits

API Request Rate instance
requests
operator-controlled (no vendor limit)
Bounded only by the self-hosted server and PostgreSQL; not capped by the software.
Message Sending Concurrency instance
workers
configured in Settings
Number of concurrent sending workers set by the operator.
Messages Per Second messenger
messages
configured in Settings
Per-messenger sliding-window send rate configured by the operator.
SMTP Provider Quota external
messages
provider-defined
Enforced by the downstream SMTP / email provider (e.g. SES, SendGrid), not by listmonk.

Policies

Operator-Controlled Throttling
Sending concurrency and per-messenger message rates are tuned by the operator under Settings.
Backoff Strategy
Clients integrating with the API should implement retries with backoff appropriate to their self-hosted instance's capacity.

Sources