Warmerly
REST API and webhooks on the Agency plan only; an MCP server on every plan.
Warmerly
Warmy
One-to-one · API access
API access
One row, in depth: what each tool does, the verified numbers, and who each suits.
Warmy details read from its pricing page, FAQ, home page, product pages and security page on 21 October 2026.
Warmerly
REST API and webhooks on the Agency plan only; an MCP server on every plan.
Warmy
Full API access listed in its plans; 90+ documented endpoints.
The short answer
API access, in one look.
Warmerly has an API and webhooks on the Agency plan only, while Warmy lists full API access in its plans and documents 90+ endpoints at 60 requests a minute. Warmerly's API runs at 60 requests a minute by default per key, and its MCP server works on every plan. Warmy is ahead on plan coverage. Last checked 22 October 2026.
WarmyWarmy ahead on this row
Full API access listed in its plans; 90+ documented endpoints.
The picture
Drawn side by side.
Who gets the API
Plans and routes
WarmerlyWarmy
Warmerly
Agency planREST API and webhooksMCP server on every plan
Warmy
Listed in its plans90+ documented endpointsA call to get access, says step one
Warmy's API page says to schedule a call for access, while its technical section says keys are generated in the workspace.
How Warmerly does it
Warmerly, in detail.
API and webhooks on Agency, an MCP server for everyone.
01
Agency plan only
API keys, the REST API and webhooks need the Agency plan. Free, Starter and Growth get a 403 error. The Agency 7-day trial includes the API.
Warmerly product, checked 21 October 2026
02
60 requests a minute by default
Each key has its own limit, 60 a minute by default, set at creation from 1 to 120, and capped at 120 on every plan.
Warmerly product, checked 21 October 2026
03
Health webhooks
Signed webhooks send mailbox health events such as score drops, authentication failures and DNS changes. They do not send opens or replies.
Warmerly product, checked 21 October 2026
04
An MCP server on every plan
Claude, ChatGPT and other MCP clients can work in a workspace on every plan, including Free.
Warmerly product, checked 21 October 2026
05
Keys are shown once
Only a SHA-256 hash of an API key is stored, and the key is shown once.
Warmerly product, checked 21 October 2026
06
Webhooks are signed
Subscriptions use signed HTTP POSTs for health events such as score drops, auto-pauses and DNS changes, sixteen event types in all.
Warmerly product, checked 21 October 2026
07
A key stops working on downgrade
An API key is only accepted while the workspace is on the Agency plan, and deliveries pause without counting as failures.
Warmerly product, checked 21 October 2026
08
MCP has its own limits
The MCP server shares one bucket of 60 calls a minute across read and write, with a lower limit on tools that send an email.
Warmerly product, checked 21 October 2026
09
OAuth 2.1 for connected apps
Connected AI apps use OAuth 2.1 with consent, and can be revoked.
Warmerly product, checked 21 October 2026
10
Idle until you ask
The API acts only on the workspace the key belongs to, and keys are listed in the workspace settings.
Warmerly product, checked 21 October 2026
11
Errors have a code
Failures return a status and an error code, with a Retry-After on limits.
Warmerly product, checked 21 October 2026
How Warmy does it
Warmy, in detail.
A documented REST API on its plans, with a call to schedule for access.
01
Full API access in the plans
The pricing page lists full API access, including n8n and similar automation platforms.
warmy.io/pricing · read 21 October 2026
02
90+ endpoints
The API page says 90+ documented endpoints across 20+ resource groups, a bearer token, an OpenAPI 3.0 file and webhooks.
warmy.io/product/api · read 21 October 2026
03
60 requests a minute
The general limit is 60 requests a minute, and 30 for domain providers. Over the limit returns a 429.
warmy.io/product/api · read 21 October 2026
04
A call to get access
Step one on the API page says to schedule a short call to get access, while its technical section says keys are generated in the workspace.
warmy.io/product/api · read 21 October 2026
05
What can be done by API
Create, read and update mailboxes, pause or resume warm-up, reconnect a mailbox, trigger a health check, set volume and schedule per mailbox, and pull deliverability, placement and health data.
warmy.io/product/api · read 22 October 2026
06
REST over HTTPS
The base URL is api.warmy.io, with JSON bodies and an OpenAPI 3.0 file.
warmy.io/product/api · read 22 October 2026
07
Keys in workspace settings
Keys are generated under Workspace, Settings, API Keys and can be revoked. Authorisation uses a bearer token and a Holder-Uid header.
warmy.io/product/api · read 22 October 2026
08
Errors have stable keys
Every failure returns a readable message and a stable error_key, with 429 and retry_after on limits.
warmy.io/product/api · read 22 October 2026
09
Zapier and Make
The integrations page names Zapier and Make, and the pricing page names n8n. The API page does not mention these three.
warmy.io/integrations/email-providers · read 22 October 2026
10
An MCP connection
The integrations page lists Warmy MCP, for Claude, Cursor or any MCP client to manage warm-up, tests and reports.
warmy.io/integrations/email-providers · read 22 October 2026
11
100M+ warm-up emails
The API page claims 100M+ warm-up emails sent and 100+ development teams that launched a tool with the API. No method is given.
warmy.io/product/api · read 22 October 2026
12
Who it is for
SaaS platforms, email and lead-generation agencies, sales infrastructure providers and enterprise teams.
warmy.io/product/api · read 22 October 2026
13
Two doc links
The page links its API documentation at two different addresses.
warmy.io/product/api · read 22 October 2026
What Warmy does not say
We looked, and found no statement on these. That is about its published pages only, not about the product.
- API pricing and what each plan includes
- Which webhook events exist
- Maximum mailboxes per workspace through the API
- The full endpoint list in writing
- Webhook event names
Where the sources disagree
We report each version rather than pick one.
- Access: the API page says to schedule a call to get access, while its technical section says keys are generated in the workspace.
- Automation: the pricing page names n8n and the integrations page names Zapier and Make, but the API page does not mention them.
The numbers
Only what we could verify.
| Measure | Warmerly | Warmy |
|---|---|---|
| API access | REST API and webhooks on the Agency plan only; an MCP server on every plan. | Full API access listed in its plans; 90+ documented endpoints. |
| API on a starting plan | No, Agency only | Included, per its pricing page |
| Requests a minute | 60 by default, up to 120 | 60 |
| Endpoints documented | Public reference pages | 90+ |
| Webhook event types | 16 | Not stated |
| Auth | X-Api-Key | Bearer token and Holder-Uid |
In practice
What it means for you.
Our reading of the facts above. Not a promise, and not the only reasonable reading.
Check the plan before you build
Warmerly's API needs the Agency plan at $179 a month. Warmy's pages list it in its plans.
Use MCP if you only need assistants
Warmerly's MCP server works on every plan for reading and acting from Claude or ChatGPT.
Check the plan before the build
A script that depends on Warmerly's API needs Agency. MCP works on every plan.
Ask about the trial
Warmy's page does not say whether API access is in the 7-day trial.
Who it suits
Pick the one that fits.
Warmerly
Warmerly is the better fit if
- You build on the API at Agency scale
- You want health webhooks
- You want an MCP server on any plan
- You want an MCP connection without paying for the Agency plan
- You want signed webhooks for health events
Warmy
Warmy is the better fit if
- You want API access without a top plan
- You want 90+ documented endpoints
- You automate through n8n and similar tools
- You want to onboard mailboxes at scale through an API
- You want automation platforms such as Zapier and Make
Questions
Does Warmy have an API?
Yes. Its API page documents 90+ endpoints at 60 requests a minute, and its pricing page lists full API access in its plans.
Does Warmerly have an API on every plan?
No. The REST API and webhooks are on the Agency plan only. The MCP server works on every plan.
What are the API rate limits?
Warmerly allows 60 requests a minute by default per key, up to 120. Warmy states 60 requests a minute.
How do you authenticate with each API?
Warmerly uses an X-Api-Key header. Warmy uses a Bearer token and Holder-Uid.
Sources
Warmy pages were read on 21 October 2026. Plans and wording change, so check the vendor's own page before you decide. Warmerly details come from the product as it runs today.
More features
See it on your own mailbox.
Connect a mailbox. Warmerly runs alongside whatever you send from now, so you can compare before you move anything.
Free plan, no card. Paid plans: 7-day trial, first charge on day 8.