# Pidgely

> Send transactional and product email with one API call. Domain authentication, reputation protection and signed webhooks built in. Free for 10,000 emails a month.

Key facts:
- Status: early access (waitlist on the home page).
- Delivers email with its own infrastructure, end to end: no third-party sending vendor underneath.
- REST API with the same send request format as Resend: POST /emails (same paths as api.resend.com), batches of up to 100 emails, scheduling and cancel, Idempotency-Key for safe retries.
- Domain authentication: DKIM signing with the customer domain, aligned SPF and DMARC, automatic DNS verification; a domain belongs to one account.
- Reputation protection: automatic handling of bounces and spam complaints, suppression lists, one-click unsubscribe (RFC 8058), gradual ramp-up for new senders, automatic pausing of risky sending.
- Delivery events delivered as webhooks signed with the Standard Webhooks specification (Resend event names and svix-* signature headers on the Resend-compatible API).
- Also: templates with variables, scheduling in natural language ("tomorrow at 9am") with cancel, SMTP relay (smtp.pidgely.com, user pidgely, password = API key), contacts, segments/audiences and broadcasts with personalization and one-click unsubscribe, email logs and delivery timeline, team members and roles.
- Official SDKs: Node.js (npm pidgely), Python (pip pidgely), Go (github.com/pidgely/pidgely-go), PHP (pidgely/pidgely-php), Ruby (gem pidgely).
- Drop-in for Resend: existing Resend SDKs (Node.js, Python, Go, PHP, Ruby, Rust, Java, .NET) also work by changing the base URL and the API key.
- Not available yet: open/click tracking, inbound email, automations. Coming soon: MCP server for AI assistants, dashboard.
- Channels: email now; SMS, WhatsApp and push planned.
- Free: 10,000 emails per month (up to 500 per day), 1 domain, webhooks and the full API. Starter: $5 per month for 50,000 emails, $0.20 per extra 1,000; Growth: $19 per month for 250,000 emails, $0.15 per extra 1,000; Scale: $59 per month for 1,000,000 emails, $0.10 per extra 1,000. Prices in US dollars.
- Contact: contact@pidgely.com · Support: support@pidgely.com · Privacy: privacy@pidgely.com · Security: security@pidgely.com · Abuse: abuse@pidgely.com
- Company: Caotec Serviços em Tecnologia Ltda, CNPJ 25.171.456/0001-45, São Carlos/SP, Brazil

## Pages

- [Email for developers.](https://pidgely.com/): Send transactional and product email with one API call. Domain authentication, reputation protection and signed webhooks built in. Free for 10,000 emails a month.
- [Pidgely blog: email deliverability for developers](https://pidgely.com/blog/): Practical guides on email deliverability, DKIM, SPF, DMARC, bounces, IP warm-up and email APIs, written by the team building Pidgely.
- [Documentation (coming soon)](https://docs.pidgely.com)
- [llms.txt · Português (Brasil)](https://pidgely.com/pt-br/llms.txt)
- [llms.txt · Español](https://pidgely.com/es/llms.txt)

## Articles (Markdown)

- [Email Feedback Loops (ARF): How to Keep Complaint Rates Low](https://pidgely.com/blog/feedback-loops-complaint-rate.md): How email feedback loops and ARF complaint reports work, how to measure complaint rate correctly, and practical ways to keep it under Gmail's 0.1% target.
- [Email Webhooks: Verifying Signatures and Handling Retries](https://pidgely.com/blog/email-webhooks-signature-verification.md): How to receive email event webhooks safely: verify Standard Webhooks signatures, block replays, handle retries and process events idempotently, with code.
- [Gmail and Yahoo Bulk Sender Requirements: The Checklist](https://pidgely.com/blog/gmail-yahoo-bulk-sender-requirements.md): A practical checklist of the Gmail and Yahoo bulk sender requirements: authentication, DMARC alignment, one-click unsubscribe, spam rate limits and DNS.
- [Hard vs Soft Bounces: SMTP Codes and Suppression Lists](https://pidgely.com/blog/hard-vs-soft-bounces.md): The difference between hard and soft bounces, how to read SMTP and enhanced status codes, and how to build suppression rules that protect your reputation.
- [How to Warm Up a New Sending IP: Schedule, Signals, Mistakes](https://pidgely.com/blog/ip-warmup-guide.md): A practical IP warm-up guide: how to ramp volume on a new sending IP, which signals to watch at each mailbox provider, and the mistakes that reset reputation.
- [One-Click Unsubscribe (RFC 8058): How to Implement It Right](https://pidgely.com/blog/one-click-unsubscribe-rfc-8058.md): Implement List-Unsubscribe and List-Unsubscribe-Post per RFC 8058: headers, DKIM signing, the POST endpoint, and how to avoid link scanners unsubscribing users.
- [Own MTA vs Email API: Costs, Control and Vendor Lock-In](https://pidgely.com/blog/own-mta-vs-email-api.md): Should you run your own MTA or use an email API? A practical comparison of costs, deliverability work, control and vendor lock-in, plus how to stay portable.
- [Shared vs Dedicated IP for Email: How to Choose](https://pidgely.com/blog/shared-vs-dedicated-ip.md): Shared vs dedicated sending IPs explained: how reputation works on each, the volume you need for a dedicated IP, costs, risks and a simple decision framework.
- [SPF, DKIM and DMARC Explained: Setup and Alignment Guide](https://pidgely.com/blog/spf-dkim-dmarc-explained.md): How SPF, DKIM and DMARC work together, how alignment really works, and a step-by-step setup with DNS records you can copy and adapt.
- [Transactional vs Marketing Email: Why Separate Your Streams](https://pidgely.com/blog/transactional-vs-marketing-streams.md): Why separating transactional and marketing email protects deliverability, and how to split streams by subdomain, IP pool, suppression scope and sending policy.
- [VERP and Automated Bounce Handling: DSN Parsing Explained](https://pidgely.com/blog/verp-bounce-handling.md): How VERP encodes the recipient in the return-path, how to parse RFC 3464 DSNs, and how to tell real bounces from auto-replies in an automated bounce pipeline.
- [Why we are building Pidgely](https://pidgely.com/blog/hello-pidgely.md): Pidgely is a developer email API that runs its own MTA. Here is why we built it, what already works today, and what comes after email.
- [Why Your Emails Go to Spam: A Troubleshooting Guide](https://pidgely.com/blog/why-emails-go-to-spam.md): Find out why your emails land in spam: a step-by-step guide to authentication, reputation, list quality, content and infrastructure, with checks to run today.

## Legal

- [Privacy Policy](https://pidgely.com/privacy/): How Pidgely handles personal data: what we collect as controller, how we process email data on behalf of our customers, legal bases, retention and your rights.
- [Terms of Use](https://pidgely.com/terms/): The rules for using Pidgely, the email API: accounts, acceptable use and anti-spam rules, plans and billing, data processing, liability and termination.
- [Cookie Policy](https://pidgely.com/cookies/): The Pidgely website uses a single, strictly necessary cookie to remember your language. No analytics, no advertising, no tracking.
- [Communications and marketing](https://pidgely.com/communications/): Which emails Pidgely sends you, what we never do with your data, and how to stop receiving product news at any time.
- [How to delete your account](https://pidgely.com/delete-account/): Delete your Pidgely account or leave the waitlist by email today, and from the dashboard soon. Data is deleted within 30 days.

## Optional

- [Full text for LLMs](https://pidgely.com/llms-full.txt)
- [Sitemap](https://pidgely.com/sitemap.xml)
- [RSS](https://pidgely.com/rss.xml)