OverviewProductsPlatformsAPI ReferenceResources

Limits & errors

Send caps, size limits and rate limits on Google accounts, what the connection cannot do, and the errors every Gmail, Calendar and Drive call can return.


Sending limits

LimitValue
Sends a day, consumer Gmail200 per mailbox
Sends a day, Google Workspace500 per mailbox
Cap resetMidnight UTC
Same body to many peopleMore than 50 distinct recipients in an hour starts a cooldown: 10 minutes, doubling up to 24 hours
RecipientsUp to 100 each in to, cc and bcc
AttachmentsUp to 20, 25 MB in total
Payment methodRequired on the workspace before the first Gmail send

Replies count as sends. A send that Gmail rejects still uses its slot.

Size and page limits

LimitValue
Email list pageUp to 200, default 50
Labels in one updateUp to 20 in addLabels and 20 in removeLabels
Draft list pageUp to 100, default 25
Calendar event pageUp to 200, default 50
File list pageUp to 100, default 50
File upload by URL100 MB, https, no redirects, 20 seconds
File upload as multipart4.5 MB request
Free-busy and availabilityUp to 10 mailboxes per request
Picker session30 minutes, single-use, up to 50 preselected files

Rate limits

Reads are live calls to Google and are not metered. They count against your API rate limit and against the mailbox's Gmail quota of 6,000 units a minute.

ReadGmail units
GET /v1/email/messages5, plus 20 per message returned
GET /v1/email/threads10, plus 40 per thread returned
GET /v1/email/threads/{threadId}120

A full 200-thread page alone is more than the minute allows, so keep limit at 50 or less when you poll.

Zernio paces list and thread reads on each mailbox against one shared budget of 4,500 units a minute, and keeps the rest for incoming mail and sends.

Reading incoming mail draws on the same budget, so a busy mailbox slows your reads first.

When a read would wait more than 15 seconds for quota, it answers 429 rate_limited with Retry-After and details.source: "zernio". When Google itself throttles, Zernio waits and retries once, then answers 429 with details.source: "provider".

What you cannot do

  • Post or schedule social content on a Google account: use the email, calendar and files endpoints.
  • Schedule an email more than 30 days ahead.
  • Send from an address that is not a verified Gmail send-as alias of the mailbox.
  • Open Drive files the user did not pick or Zernio did not create. Use a picker session.
  • Write contacts back to Google: the sync is read-only.
  • Remove one area from an account. Disconnect it and connect again with the areas you want.

Common errors

ErrorCauseFix
400 invalid_field_valueA field is invalid, scopes is missing on connect, or teams conferencing on GoogleFix the field named in param.
400 platform_not_supportedThe account is not a Google or Microsoft accountUse the accountId of a mailbox.
401 reconnect_requiredGoogle refused the account's accessReconnect the account.
402 payment_requiredGmail send without a payment method on the workspaceAdd a card, then send again.
404 resource_not_foundThe message, event or file does not exist, or reason: "file_not_granted" on DriveCheck the id, or let the user pick the file.
412 account_scope_missingThe account lacks the area this call needs. details has grantedAreas and missingAreaConnect again with the area added.
429 email_send_cap_reachedToday's send cap is used upWait for resetsAt.
429 rate_limitedA sending cooldown, or Google throttlingWait for Retry-After.
502 platform_api_errorGoogle returned an error Zernio does not mapRetry. The message carries Google's.
Was this page helpful?

On this page