Gmail Quickstart

No domain, no DNS, no SMTP settings. Connect the Gmail account you already have and send through the same API, logs, and events as production senders.

1. Connect Gmail

In your project dashboard, choose Connect Gmail (rolling out to early access projects now). Google asks for one permission — sending mail on your behalf — and nothing else. We never see, ask for, or store your Google password; the authorization token is encrypted at rest and you can revoke it anytime from either side.

2. Send exactly like everyone else

// Node 18+, no dependencies
const res = await fetch("https://api.calder.click/v1/emails", {
  method: "POST",
  headers: { /* key + Idempotency-Key */ },
  body: JSON.stringify({
    from: "myproject@gmail.com", // your connected address
    to: "customer@example.com", /* subject, html */
  }),
});
// 202 — queued. SDKs land with v1.

3. Know the limits (they’re the point)

Gmail sending is capped daily and rate-limited on purpose — it’s the on-ramp, not bulk infrastructure. Your dashboard always shows usage against the cap before you hit it. Hitting it regularly is the signal to graduate:

Rules of the road

• Send only as your connected address — anything else is rejected.
• Transactional mail only. Newsletters and bulk sends will get throttled, then suspended.
• Revoking in Google or in Calder takes effect immediately.