Loops · Rate Limits

Loops Rate Limits

Loops publishes two distinct API throttles plus separate email-sending and webhook-delivery rates. The API baseline is 10 requests per second per team. The content API — campaigns, campaign groups, components, email messages, themes, transactional emails, transactional groups, uploads and workflows — is throttled far more tightly at 60 requests per 60 seconds per team. Every response carries x-ratelimit-limit and x-ratelimit-remaining, and exhaustion returns 429 Too Many Requests. Separately, email sending is capped at 10 emails/second on free plans and 1,000 emails/second on paid plans, with excess queued rather than rejected, and webhook events are delivered at a maximum of 10 per second.

Loops Rate Limits is the machine-readable rate-limit profile for Loops on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 8 rate-limit definitions, measuring requests, emails, events, previews, and uploads.

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

Tagged areas include Email Marketing, Transactional, Automation, SaaS, and Campaigns.

8 Limits Throttle: 429
Email MarketingTransactionalAutomationSaaSCampaignsRate LimitingQuotasThrottling

Limits

Default API rate limit team
requests · second
10
Baseline per team. Higher limits available on request to Loops support.
Content API rate limit team
requests · 60 seconds
60
Effectively 1 request/second sustained on the content surface — six times tighter than the baseline. This is the limit that matters for any agent or migration job editing campaigns, themes or workflows in bulk.
Email sending rate — free plan team
emails · second
10
Excess is queued until it can be sent, not rejected.
Email sending rate — paid plans team
emails · second
1000
Excess is queued until it can be sent, not rejected.
Webhook delivery rate account
events · second
10
Further events are queued.
Free plan monthly send allowance team
emails · 30 days
4000
Marketing and transactional combined. Paid plans have no send cap.
Email message preview limit team
previews · day
A daily preview cap exists and returns 429 on previewEmailMessage, but the numeric value is not published. Recorded as an honest null rather than a guess.
Upload limit team
uploads · unspecified
An upload cap exists and returns 429 on createUpload; the value is not published.

Policies

Backoff Strategy
Loops recommends retries with exponential backoff on 429. No Retry-After header is provided, so backoff must be client-chosen; add jitter.
Higher Limits
Contact Loops support (https://app.loops.so/settings?page=support) to discuss an increased limit.
Queue-not-reject on sending
Send-rate limits queue rather than fail, so a burst of transactional sends is delayed, not dropped. API rate limits do reject with 429.

Sources