# Zoho CPaaS (formerly ZeptoMail) > Transactional email service from Zoho, renamed from ZeptoMail to Zoho CPaaS in September 2026. It sends application email through a REST API or SMTP relay, with templates, domain management, suppression lists, logs and webhooks. - Canonical: https://www.anchorterminal.com/tools/zoho-zeptomail - Markdown: https://www.anchorterminal.com/tools/zoho-zeptomail.md (~7,850 tokens) - Slim: https://www.anchorterminal.com/tools/zoho-zeptomail.min.md (~1,830 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/zoho-zeptomail.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade C · 61.8/100 · rank #356 of 722 · #10 in Email delivery APIs · not agent-ready · confidence medium** More from Zoho Corporation, listed separately because each is its own product: [Zoho Books](https://www.anchorterminal.com/tools/zoho-books.md) (Accounting & invoicing), [Zoho CRM](https://www.anchorterminal.com/tools/zoho-crm.md) (CRM & customer platforms), [Zoho Recruit](https://www.anchorterminal.com/tools/zoho-recruit.md) (Recruiting & applicant tracking), [Zoho People](https://www.anchorterminal.com/tools/zoho-people.md) (HR & employee operations). ## Assessment A public OpenAPI 3.0 file covers all 42 operations, and each Agent has its own send-only key. Email costs $2.50 per 10,000 with the first credit free. No API rate limit, 429 handling, idempotency key or SLA was found in the reviewed documentation, and new accounts wait for a manual review. ## Facts | Field | Value | | --- | --- | | Vendor | Zoho Corporation (https://www.zoho.com/cpaas/) | | Kind | HTTP API | | Category | Email delivery APIs (https://www.anchorterminal.com/categories/email) | | Transport | HTTP | | Endpoint | `https://cpaas.zoho.com/v1.1` | | Auth | OAuth or key · Sending takes a send key in the `Authorization` header with the prefix Zoho-enczapikey. Each Agent has its own keys, one set per channel, copied from the console's SMTP/API tab or created and deleted by API. Logs, domains, templates, agents and suppression lists take a Zoho OAuth 2.0 access token (authorisation code grant, one-hour tokens, refresh tokens) with per-resource scopes. Access is self-serve, but every new account passes a manual review that the docs say takes two business days. | | Pricing | Pay per use ($30 / mo) · $2.50 per email credit of 10,000 emails ($0.25 per 1,000), valid six months, counted per recipient. The first credit is free, and a sandbox Agent accepts 10,000 test emails a day without sending them. No monthly plan. Credits can be bought only after the account review. Dedicated IP $30 a month, billed annually. Prices are filled in by script from a public JSON file (https://www.zoho.com/cpaas/pricing.html). | | x402 | No · No x402, MPP or L402 in the API docs, the OpenAPI file or the pricing page (checked 2026-10-08). | | Licence | Proprietary service under the Zoho CPaaS terms of use. The Node SDK on npm is MIT | | Packages | npm: `zeptomail` | | Docs | https://www.zoho.com/cpaas/help/api/api-home.html | | llms.txt | https://www.zoho.com/cpaas/llms.txt | | npm downloads / week | 40,110 | | Rename | ZeptoMail became Zoho CPaaS in September 2026, adding SMS (India only), WhatsApp and voice, all three marked beta. zoho.com/zeptomail redirects to zoho.com/cpaas. api.zeptomail.com still answered on 8 October 2026 | | API | REST, version 1.1, 42 operations in one OpenAPI 3.0.3 file. 33 cover email (send, batch, templates, file cache, logs, domains, agents, suppressions), 9 cover voice, SMS and WhatsApp | | Regions | Six data centres with their own base URL. US cpaas.zoho.com, EU cpaas.zoho.eu, India cpaas.zoho.in, Australia cpaas.zoho.com.au, Japan cpaas.zoho.jp, China cpaas.zoho.com.cn | | Credentials | Send key per Agent and per channel in the `Authorization` header with the prefix Zoho-enczapikey. Zoho OAuth 2.0 (authorisation code grant, one-hour access tokens, refresh tokens) for management calls, with scopes such as Zeptomail.Domains.READ | | SMTP | smtp.zeptomail.com on port 587 (TLS) or 465 (SSL), username emailapikey, TLS 1.2 | | Limits | 500 addresses per to, cc or bcc field, 60 attachments, 15 MB per attachment, 500 characters in a subject. No request rate limit found. An owner can set a daily blocking limit per Agent | | Free allowance | First credit free, 10,000 emails. Unreviewed accounts have a daily sending limit and can't buy credits | | Sandbox | Up to 2 sandbox Agents, 10,000 emails a day each, nothing sent to recipients, simulated bounces and webhooks | | Logs | Email logs kept 60 days and readable by API with offset, limit and 13 filters. Content is stored only if the owner opts in. Account activity logs kept one year | | Webhooks | Soft bounce, hard bounce, open, click and feedback loop events per Agent | | Inbound | None | | Dedicated IP | $30 a month, billed annually, in some data centres | | SDK | Node package zeptomail 8.0.1 (29 May 2026, MIT, Node 20 or later, TypeScript types). Code samples for curl, C#, Python, PHP and Java, and a Postman collection | | Certifications | Zoho lists SOC 2 Type II, SOC 1 Type II, ISO/IEC 27001, 27701, 27017 and 27018 on its compliance page, and runs a bug bounty at bugbounty.zohocorp.com | | Capabilities | email.send, email.templates, email.domains, email.analytics | | Tags | hosted, usage, openapi, llms-txt, oauth, smtp, webhooks, sandbox, typescript, status-page, bug-bounty, soc2 | | JSON | https://www.anchorterminal.com/api/v1/tools/zoho-zeptomail.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 41 | 8.2 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 78 | 12.7 | | Agent ergonomics | 13% | 16.2 | 55 | 8.9 | | Security & auth | 14% | 17.5 | 76 | 13.3 | | Payments & pricing | 10% | 12.5 | 40 | 5.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 74 | 6.5 | | Transparency & trust (editorial 69, provenance 94) | 7% | 8.8 | 82 | 7.2 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **61.8 → C** | ### Why each score - Reliability 41: Graded on the hosted email API with the hosted lines. Zoho's status site at us.zohostatus.com lists three Zepto Mail components with status and incident history sections (20). The history loads by script and we couldn't read it. The site's RSS feed shows Zepto Mail and Zepto Mail-SMTP last changed status on 29 July 2026, in the same minute as several other Zoho services, with no duration, so this line is scored as no readable history (5). No request rate limit was found. The docs give payload caps (500 addresses a field, 60 attachments, 15 MB each) and the sandbox allowance of 10,000 emails a day (6). No 429 handling, Retry-After or idempotency key found in the docs or the OpenAPI file, whose email operations document only 200, 400 and 404 (0). No SLA found (0). The email channel is generally available, while SMS, WhatsApp and voice are marked beta (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 78: One public OpenAPI 3.0.3 file with 42 operations, linked from the docs without a login (25). llms.txt at zoho.com/cpaas/llms.txt and a second for the help centre, with a Markdown copy of each page (10). Every operation has a description, most of them one sentence, with nothing on when not to use it (10). Request bodies name required fields and length caps, with 9 enums across the file, but log filters take dates as free strings and responses are typed as a bare JSON object (10). Sample requests and responses on every page and an error-code table of 24 rows with remedies. The 401 body we got from the live endpoint has a different shape from the documented sample (11). Version 1.1 in the path and a What's New page dated by month only (12). - Agent ergonomics 55: Send responses are small, and the logs endpoint takes offset and limit, with no field selection (15). Thirteen filters on email logs, among them recipient, subject, date range, `client_reference` and bounce or delivery state (16). Errors carry a code, a sub-code and a message, and the docs pair each with a fix (16). No idempotency key and no guidance on retrying a send (0). A send needs only from, to and subject. The one official SDK found is for Node, and managing the account needs a second credential type (8). - Security & auth 76: Send keys are per Agent and per channel, can be created, listed and deleted by API, and can only send and upload attachments. Management calls use Zoho OAuth 2.0 with READ, CREATE, UPDATE and DELETE scopes per resource and one-hour access tokens. That earns 30, less 10 because the OAuth guide documents the client secret and refresh token in the token URL's query string (20). Read-only scopes, send-only keys, sandbox Agents and IP allow lists for sending, the REST API and the web console. No approval step for deletes (15). No inbound mail, so responses hold only the account's own logs and settings (10). Activity logs per user kept one year with export, and email logs for 60 days that show the triggering IP (13). security.txt valid until 30 June 2028, a bug bounty, and SOC 2 Type II and ISO/IEC 27001 on Zoho's compliance page. No public advisory feed found (18). - Payments & pricing 40: No x402, MPP or L402 (0). $2.50 per credit of 10,000 emails and $30 a month for a dedicated IP, public without a login (20). The first credit is free, and the documented signup asks for a phone verification and no payment details (20). Signup is a browser form with phone verification, and Zoho staff review each new account, so there is no autonomous route (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 74: The What's New page dates entries by month. The newest is the September 2026 rename with new SMS, WhatsApp and voice endpoints, and help pages carry dates up to 6 October 2026, so we counted it as within 30 days (30). Entries for September, August and July 2026 fall in the last 90 days, though the July one may predate 10 July (20). A public changelog, a support address and a contact page that says support runs around the clock. We saw no public forum replies (10). The Node SDK zeptomail 8.0.1 is from 29 May 2026 with about 40,000 weekly downloads, and it is the only official SDK found (10). The npm package names no source repository, so CI and dependency health couldn't be read (4). - Transparency & trust 82: Closed service with its own published terms of use, and an MIT Node SDK (20). Zoho's privacy policy of 22 December 2025 covers service data, and the CPaaS pages say content is stored only on opt-in for 60 days and logs for 60 days. The pages disagree on deletion. The GDPR page says account data is deleted within 24 hours of a 48-hour grace period, the privacy policy says a clean-up every six months with backups three months later, and the April 2026 changelog entry says content can be kept up to 50 days (18). The terms commit to a six-month deprecation period after a service announcement, with no dated notices to check it against (16). Six data centre regions are named with their hosts, and Zoho publishes a sub-processor directory by service that loads by script and that we couldn't read (15). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (19 items): https://www.anchorterminal.com/fixes/zoho-zeptomail.md (JSON https://www.anchorterminal.com/fixes/zoho-zeptomail.json) ### What we couldn't check - The lead named the product Zoho ZeptoMail. It was renamed Zoho CPaaS in September 2026, and the API host in the docs is now cpaas.zoho.com - unchecked: incident history on us.zohostatus.com, which loads by script. Only the RSS feed's last status change (29 July 2026) was read - unchecked: Zoho's sub-processor directory entries for Zoho CPaaS, which load by script - unchecked: whether the Zoho MCP product listed on the status page exposes Zoho CPaaS. Nothing in the CPaaS docs mentions an MCP server - Whether a request rate limit exists and what a throttled call returns - Whether signup ever asks for a card. The documented steps don't - The day in September 2026 of the rename, and whether the July 2026 changelog entry falls inside the last 90 days - Whether bounced or rejected sends use credit - No data processing addendum was looked for beyond the GDPR page - `lastRelease` is left empty because the newest changelog entry is dated September 2026 with no day. The newest release with a full date is the Node SDK 8.0.1 on 29 May 2026 ### Sources - home page with the rename notice: (seen 2026-10-08) - API overview and groups: (seen 2026-10-08) - API index with OAuth scopes: (seen 2026-10-08) - authentication: (seen 2026-10-08) - OAuth guide: (seen 2026-10-08) - send email reference: (seen 2026-10-08) - error codes: (seen 2026-10-08) - OpenAPI file: (seen 2026-10-08) - llms.txt: (seen 2026-10-08) - data centres and base URLs: (seen 2026-10-08) - pricing: (seen 2026-10-08) - price values the pricing page loads: (seen 2026-10-08) - subscription and credits: (seen 2026-10-08) - getting started and account review: (seen 2026-10-08) - sandbox Agent: (seen 2026-10-08) - What's New: (seen 2026-10-08) - terms of use: (seen 2026-10-08) - Zoho privacy policy: (seen 2026-10-08) - GDPR page: (seen 2026-10-08) - IP restrictions: (seen 2026-10-08) - activity logs: (seen 2026-10-08) - status page: (seen 2026-10-08) - status RSS feed: (seen 2026-10-08) - security.txt: (seen 2026-10-08) - compliance page: (seen 2026-10-08) - npm registry record for zeptomail: (seen 2026-10-08) - contracting entities: (seen 2026-10-08) ## Who's behind it (provenance 94/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Zoho Corporation | 20/20 | | Domain age | zoho.com, registered 2004-01-16 (22 years) | 15/15 | | Endpoint on the vendor's domain | cpaas.zoho.com | 15/15 | | Terms of service | read, states 2 of the 7 things a reader expects | 5.7/10 | | Privacy policy | read, states 8 of the 8 things a reader expects, and has 1 clause that costs points | 8/10 | | Status page | us.zohostatus.com | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | The Zoho CPaaS terms of use name the contracting party as the Zoho entity for the customer's region. That is Zoho Corporation for the United States and Zoho Corporation Private Limited for India (https://www.zoho.com/legal/zoho-contracting-entities.html). The privacy field points at Zoho's privacy policy, last updated 22 December 2025, whose Part II covers the data customers process through Zoho services. Zoho CPaaS has no privacy policy of its own. status.zoho.com redirects to us.zohostatus.com, which lists Zepto Mail, Zepto Mail-SMTP and Zepto Mail-SMTP (PORT:465) under the old name. Other regions have their own status sites. www.zoho.com/.well-known/security.txt names security@zohocorp.com and the bug bounty, and expires on 30 June 2028. cpaas.zoho.com/.well-known/security.txt returns 403. RDAP for zoho.com gives a registration date of 2004-01-16. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.zoho.com/cpaas/terms.html), read 2026-10-08, gives no date, states 2 of the 7 things a reader expects. - To know. Says access can be ended without notice or for any reason. "If your use of Zoho CPaaS is found to be in violation of these Terms, Zoho may, in its sole discretion, take appropriate action against you, which may include suspension or permanent termination of your access to the relevant Channel or to your user account, without any prior notification." - Not found in the text. Gives the date it was last updated. - Not found in the text. Names the governing law or courts. - Not found in the text. States a limit on its liability. - Not found in the text. Says how changes to the terms are announced. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). Zoho may monitor account activity and email content, manually and with automated tools, and may throttle emails. "In order to prevent spam and to detect possible violation of these Terms, Zoho reserves the right to monitor your account activities and email content both manually and through automated tools." - Also in the text (2026-10-08). The customer must not try to reach any API functionality that the API documentation does not expose. "You must not try to access any functionality that is not exposed in the documentation for the API." - Also in the text (2026-10-08). Unused credits are not refunded when the customer closes the account, and credits used without authorisation are not refunded. "Zoho shall not provide any refund for (i) any unauthorized use of your service credits, either knowingly or unknowingly; and (ii) unused credits in your Zoho CPaaS account in the event of your closure of your Zoho CPaaS account" **Privacy policy** (https://www.zoho.com/privacy.html), read 2026-10-08, dated 2025-12-22, states 8 of the 8 things a reader expects. - To know. Says it may use customer content to train or improve models, and no opt-out was found (costs points). "In keeping with Zoho's promise not to exploit your data in a way that is not respectful of your privacy and confidentiality expectations, we make only the following limited use of service data for these technologies: (i) using anonymized crops of service data to improve accuracy of the algorithms;" - Gives the date it was last updated. Last updated 2025-12-22. - Says how long data is kept. Names a period of 6 months. - Gives a privacy contact. privacy@zohocorp.com. - Says where data is transferred or stored. Data goes to the United States. - Also in the text (2026-10-08). Zoho employees and contractors may open service data to resolve errors and to check by hand emails reported as spam and scanned images. "so that they can (i) identify, analyze and resolve errors, (ii) manually verify emails reported as spam to improve spam detection, or (iii) manually verify scanned images that you submit to us to verify the accuracy of optical character recognition." - Also in the text (2026-10-08). Zoho says it uses an organisation's data to develop models specific to that organisation. "(ii) using your organization's data for developing models specific for your organization." - Also in the text (2026-10-08). After an account is terminated, data leaves the active database at a clean-up run once every six months and leaves backups three months later. "Once you terminate your Zoho user account, your data will eventually get deleted from active database during the next clean-up that occurs once in 6 months." ## Live (updated 2026-10-08 20:21 UTC) - Right now: up, HTTP 403, 419 ms, checked 2026-10-08 20:21 UTC (get on `https://cpaas.zoho.com/v1.1`, asks for auth) - Uptime 24h 100.0% (32 probes) · 30 days 100.0% (32 probes) · p50 433 ms · p95 590 ms - Vendor status page: unknown, no machine-readable status found - Watching changelog - Watching pricing - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/zoho-zeptomail.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Email credit | $0.25 | per 1,000 emails | $2.50 per credit of 10,000 emails, valid six months, counted per recipient. First credit free | | Dedicated IP | $30 | per month (plan) | Billed annually, some data centres only | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Public OpenAPI 3.0.3 file with 42 operations, plus llms.txt and a Markdown copy of every help page - Send keys are per Agent and per channel and can only send. Management calls use OAuth with READ, CREATE, UPDATE and DELETE scopes per resource - Published price of $2.50 per credit of 10,000 emails, valid six months, with the first credit free - IP allow lists for sending, the REST API and the web console, and activity logs kept for one year - The terms commit to a six-month deprecation period for a retired API version ## Weaknesses - No API rate limit, 429 behaviour or Retry-After was found in the reviewed documentation or the OpenAPI file - No idempotency key on send. `client_reference` is a tracking label only - Every new account is reviewed by Zoho staff, which the docs say takes two business days, before credits can be bought - The only official SDK found is the Node package, last published on 29 May 2026 and still named zeptomail - The OAuth guide puts the client secret and refresh token in the token URL's query string - No inbound email, and no SLA was found ## Before you call it (notes for agents) 1. Call the base URL for the account's region (cpaas.zoho.com, .eu, .in, .com.au, .jp or .com.cn). A key from one region fails on another 2. Send with `Authorization: Zoho-enczapikey `. Logs, domains, templates, agents and suppressions need a Zoho OAuth token as `Authorization: Zoho-oauthtoken ` 3. Post OAuth client secrets and refresh tokens in the request body, not the query string the guide shows, so they stay out of logs 4. Don't retry a timed-out send blindly. There is no idempotency key, so look the message up by `client_reference` in the email logs first 5. Count one email per recipient, including cc and bcc, and keep each address field to 500 entries and each attachment to 15 MB 6. Use a sandbox Agent for tests. It accepts up to 10,000 emails a day and sends none of them ## Connect Install: ```bash npm install zeptomail ``` First request: ```bash curl --request POST --url https://cpaas.zoho.com/v1.1/email \ --header 'Authorization: Zoho-enczapikey REPLACE_WITH_YOUR_KEY' \ --header 'content-type: application/json' \ --data '{"from":{"address":"hello@yourapp.com","name":"Your App"},"to":[{"email_address":{"address":"user@example.com","name":"User"}}],"subject":"Test Email","htmlbody":"

Test email sent successfully.

"}' ``` Through letme (picks today, calling later): https://letme.dev/zoho-zeptomail. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Amazon SES | BB | 75.1 | 48 | email.send, email.templates, email.domains, email.analytics | no | https://www.anchorterminal.com/tools/amazon-ses.md | | Resend API + MCP | BB | 75.1 | 50 | email.send, email.templates, email.domains, email.analytics | no | https://www.anchorterminal.com/tools/resend.md | | MailerSend | B | 69.5 | 156 | email.send, email.templates, email.domains, email.analytics | no | https://www.anchorterminal.com/tools/mailersend.md | | Mailtrap Email API + MCP | B | 66.8 | 228 | email.send, email.templates, email.domains, email.analytics | no | https://www.anchorterminal.com/tools/mailtrap.md | | Postmark API + MCP | B | 66.5 | 235 | email.send, email.templates, email.domains, email.analytics | no | https://www.anchorterminal.com/tools/postmark.md | | Mailgun API + MCP | B | 66.2 | 242 | email.send, email.templates, email.domains, email.analytics | no | https://www.anchorterminal.com/tools/mailgun.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - ZeptoMail was renamed Zoho CPaaS in September 2026, and existing agents, domains, templates and settings carry over unchanged (source: ) - Send, batch, template and file-cache calls take a per-Agent send key, while logs, domains, agents, templates and suppressions take Zoho OAuth with scopes per resource and operation (source: ) - The OpenAPI 3.0.3 file lists 42 operations, 33 of them for email (source: ) - One email credit covers 10,000 emails for six months, usage is counted per recipient, and the first credit is free (source: ) - Every new account is reviewed by Zoho staff through a customer validation form, and credits can't be bought until then (source: ) - The terms allow only transactional email and set limits of 5 per cent bounces and 0.1 per cent spam complaints, above which Zoho may close the account without notice (source: ) ## Compare - [Amazon SES vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/amazon-ses-vs-zoho-zeptomail.md): BB 75.1 vs C 61.8 - [Brevo API + MCP vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/brevo-vs-zoho-zeptomail.md): E 44.8 vs C 61.8 - [Cloudflare Email Service vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-zoho-zeptomail.md): B 67.3 vs C 61.8 - [Loops API + MCP vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/loops-vs-zoho-zeptomail.md): B 62.7 vs C 61.8 - [MailerSend vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/mailersend-vs-zoho-zeptomail.md): B 69.5 vs C 61.8 - [Mailgun API + MCP vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/mailgun-vs-zoho-zeptomail.md): B 66.2 vs C 61.8 - [Mailjet API + MCP vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/mailjet-vs-zoho-zeptomail.md): C 59.4 vs C 61.8 - [Mailtrap Email API + MCP vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/mailtrap-vs-zoho-zeptomail.md): B 66.8 vs C 61.8 - [Mailchimp Transactional (Mandrill) vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/mandrill-vs-zoho-zeptomail.md): C 58.1 vs C 61.8 - [Postmark API + MCP vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/postmark-vs-zoho-zeptomail.md): B 66.5 vs C 61.8 - [Resend API + MCP vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/resend-vs-zoho-zeptomail.md): BB 75.1 vs C 61.8 - [Twilio SendGrid vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/sendgrid-vs-zoho-zeptomail.md): B 63.6 vs C 61.8 - [SMTP2GO API + MCP vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/smtp2go-vs-zoho-zeptomail.md): D 53.1 vs C 61.8 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on zoho.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "zoho-zeptomail", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Zoho CPaaS (formerly ZeptoMail) on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Zoho CPaaS (formerly ZeptoMail) on Anchor Terminal](https://www.anchorterminal.com/badges/zoho-zeptomail.svg)](https://www.anchorterminal.com/tools/zoho-zeptomail) ``` Plain link: ```html Zoho CPaaS (formerly ZeptoMail) on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Zoho CPaaS (formerly ZeptoMail) is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/zoho-zeptomail-dark.png - Light: https://www.anchorterminal.com/assets/share/zoho-zeptomail-light.png