Send an email on the user's behalf from their address. (docs)
POST /users/{userId}/messages/send
🔴 high
✅ yes
Connecting it
You provide: Google account (OAuth)
Where to get it: Google Cloud Console → enable Gmail API → OAuth consent screen → Credentials → Create OAuth client ID. Gmail read scopes are RESTRICTED and require security review for production.
Account needed: A Google account plus a Google Cloud project with the Gmail API enabled.
App registration: Create an OAuth client ID (Web application); configure consent screen with scopes, authorized domains, redirect URIs.
Verification required: Gmail read scopes (gmail.readonly) are RESTRICTED: production use requires brand verification PLUS an annual third-party CASA security assessment (Letter of Assessment, renewed yearly) if mail data is stored/transmitted on your servers. gmail.send alone is SENSITIVE (verification + brand, no CASA).
Testing: Unverified 'Testing' apps are capped at 100 test users with 7-day refresh-token expiry; not shippable to production.
Limits
1,200,000 quota units/min per project; 6,000/min per user. messages.send costs 100 units; 500 recipients/message max.