Guide
Gmail API sending limit: what the API changes, and what it does not
Two different limits get mixed up: how fast an app may call Google, and how much a mailbox may send. Only the second decides how many emails go out.
Short answer
No, the API does not raise it. The Gmail API quota limits how fast an app may make requests for one user [1]; it is not a sending allowance. Your mailbox keeps its own daily sending limit: 2,000 a day for a paid Google Workspace account [2], about 500 for a personal Gmail account [3]. Google's Workspace limits page lists the Gmail API among the ways of sending it covers [4].
Two limits, two purposes
| API quota | Sending limit | |
|---|---|---|
| What it limits | Requests an app makes for one user, per minute [1] | Emails and recipients a mailbox sends per day |
| Measured in | Quota units; each kind of request costs a different number [5] | Messages and recipients |
| Personal Gmail | Same API quota | About 500 emails a day [3] |
| Google Workspace | Same API quota | 2,000 a day [2]; 500 on a trial account [6] |
| What happens at the limit | Requests are refused for a short while, then work again | No new emails for up to 24 hours [7] |
The arithmetic
As of 1 October 2026, Google's quota page gives each user 6,000 quota units per minute in a project, and a
messages.send request costs 100 units [5]. That is 6,000 / 100 = 60 sends a minute
before the API pushes back. At that pace a Workspace mailbox would reach its 2,000-a-day sending limit in about 34
minutes. The API is never the bottleneck; the mailbox is. Google updated these quotas on 1 May 2026 and says older
projects keep their previous ones, so check the page for your own project.
What this means for cold email
- Do not plan around the API number. 60 a minute is a ceiling on requests, not a pace that is safe to send at.
- Do not plan around the sending limit either. 2,000 a day is the point where Google stops you, and a cold email sent anywhere near it will draw spam reports long before. See the 5,000 rule, with the arithmetic for where Google's stricter rules start.
- Space the emails out. A person does not send forty emails in a minute. Sending through the API makes it easy to do exactly that, so the pacing has to be in your software.
- Treat a refusal as a stop sign. If the API or the mailbox says no, wait. Retrying at once is how a short pause becomes a 24-hour one.
How Honest Intros uses the API
Honest Intros sends through the Gmail API from the mailbox you signed in with, one email at a time, spaced through the recipient's working hours. It starts at 20 emails a day and never sends more than 50, follow-ups included, which is a small fraction of either limit. When Google refuses a send, the email is held and tried later, never resent on a guess.
Questions
How many emails a day can I send with the Gmail API?
The same number as from the Gmail website: 2,000 a day on a paid Google Workspace account and about 500 on a personal Gmail account. The API quota limits requests per minute, not emails per day.
What is the Gmail API quota per user?
As of 1 October 2026, 6,000 quota units per minute per user in a project, and a messages.send request costs 100 units, so about 60 sends a minute. Projects that used the API before May 2026 may keep older quotas.
Does the Gmail API bypass Gmail's sending limits?
No. Google's Workspace limits page lists messages sent with the Gmail API among the sending it limits.
Is the Gmail API better than SMTP for cold email?
It sends from the same mailbox under the same daily limits. Its advantage is that the app never needs your password: you grant access through Google's consent screen and can revoke it at any time.
See what it would write for you
Type your website. Honest Intros reads it and shows the kind of first email it writes, quoting your own pages.
Free to start. Nothing is sent until you approve it.