Limits & Quotas

Overview of API rate limits, request payload limits, and daily Gmail quotas.

The following limits apply to accounts to ensure platform stability and protect fair usage. Pro plan upgrades increase these limits significantly.

API Rate Limits

EndpointFreeProWindowKeyed By
POST /api/send30 req300 reqper minuteAPI key
Gmail sender burst1 send/s personal · 2 sends/s Workspace1 send/s personal · 2 sends/s Workspace1-second sliding windowConnected Gmail account

When a rate limit is hit, the API returns 429 Too Many Requests with a Retry-After header indicating how many seconds to wait.

The per-minute API-key limit and the Gmail sender burst limit are separate. Sendlib waits up to 3 seconds for a Gmail sender slot. If no slot becomes available, the request is recorded as failed and returns 429 with Retry-After: 1. Clients should serialize sends per connected Gmail account or retry 429 responses after the indicated delay. For larger recipient lists, use /api/batch.

Request Payload Limits

FieldFreeProNotes
subject998 chars998 charsRFC 2822 maximum
html2 MB5 MBUTF-8 encoded
text1 MB2 MBUTF-8 encoded
to / cc / bcc50 each50 eachString or array of strings
attachments5 files · 1 MB/file20 files · 10 MB/fileBase64-encoded. 25 MB total cap enforced by Gmail.

Account & Daily Limits

ResourceFreeProNotes
Connected Gmail Accounts350Per Sendlib user account
Active API Keys5100Per Sendlib user account
Monthly Sending Limit3,500 emails / monthUnlimitedResets monthly based on your account sign-up date
Email Log Retention5 days90 daysLogs are automatically deleted after this period
Personal Gmail (@gmail.com)200 emails / day500 emails / dayResets daily at UTC midnight. Google hard cap is 500.
Google Workspace Account1,000 emails / day2,000 emails / dayResets daily at UTC midnight. Google hard cap is 2,000.

Daily sending quotas are set and enforced directly by Google's Gmail API. Sendlib monitors your send volume and resets your limit tracking daily at UTC midnight.

A successful Sendlib response means Gmail accepted the message and returned a message ID. It does not guarantee inbox placement: Gmail and the recipient's mail provider can still place the message in Spam based on sender reputation, message content, links, recipient engagement, and other signals. Use a consistent sender, include useful plain-text content, avoid link-heavy or image-heavy messages, and use an authenticated Google Workspace custom domain when dependable business deliverability is important.