The Problem

SCANNERS

Security Scanners Click Every Link

Proofpoint, Mimecast, Barracuda and Microsoft Defender may follow links before the recipient ever sees the email. Those clicks can enter your reporting as engagement even though no human clicked.

APPLE MPP

Apple MPP Pre-Loads Every Pixel

iOS 15+ routes opens through the Apple proxy, pre-loading all pixels regardless of whether the recipient reads. A 50% open rate may be much lower in reality.

BOTNETS

Botnets Inflate Clicks for Ad Revenue

Newsletter ad networks are targeted by botnets: diverse IPs, legitimate user agents, realistic intervals. Invisible to simple rules.

The Data Behind It

First-party findings from The State of Email Bots 2026, each drawn from a separate Omnivery dataset covering our own sending and the traffic screened by this API. Automated opens have been a known problem since Apple MPP. The data now shows significant contamination of clicks as well. Also available as a 10-page PDF.

~50%
of B2C email opens are non-human, unchanged since Apple MPP landed
16%
of B2C clicks are now bots, up from about 2% in 2023
50%
of clicks screened by this API were bots by June 2026, up from 34%
~30%
bot clicks at Outlook, against 2% to 4% at Yahoo and GMX

What the API Detects

  • Security scanner clicks. Proofpoint, Mimecast, Barracuda, Microsoft Defender, and others.
  • Apple MPP automated opens. Proxy-loaded pixel requests from Apple's infrastructure account for 95+% of the non-human opens Omnivery identifies (in B2C). These are relatively straightforward to identify. Clicks are significantly harder because they originate from security scanners, tracking tools and sophisticated botnets.
  • Inbox tracking tools. Automated tools for email research, competitive intelligence, deliverability testing.
  • Malicious botnets. Coordinated automated click campaigns targeting ad network monetization.
  • Other non-human interaction patterns. Identified through 20+ proprietary datasets developed over 8+ years.

The detection engine combines IP reputation, user agent analysis, behavioral pattern matching, and honeypot data, which is what allows it to separate automated interactions from human ones across all of the sources above.

How It Works

Two Integration Modes

Batch mode: Up to 500 events, async webhook delivery for high-volume processing.

Single interaction mode: Synchronous, 1s+ minimum response time, rate limited - not for real-time inline filtering.

Authentication

ov-token header. Access requires explicit enablement per domain. Contact sales@omnivery.com.

Minimal Integration Requirements

Each event requires only three fields: ip, uas, event_id. More fields = higher accuracy.

{
  "events": [
    {
      "ip": "156.17.201.170",
      "uas": "Mozilla/5.0 (iPhone; CPU iPhone OS 16_5 ...)",
      "event_id": "unique-event-identifier-123",
      "action": "click",
      "domain": "example.com",
      "recipient_id": "hashed-recipient-id",
      "message_id": "message-identifier",
      "ts": 1721474736
    }
  ],
  "webhook_url": "https://your-endpoint.com/bot-results"
}

The Response

is_bot: true or is_bot: false. Clean, unambiguous, actionable.

{
  "is_bot": false,
  "request": {
    "action": "click",
    "event_id": "57d476d4-d8db-4757-b4da-5f2b8d6bf5f5",
    "ip": "156.17.201.170",
    "uas": "Mozilla/5.0 (iPhone; CPU iPhone OS 16_5 ...)",
    "message_id": "17690841631",
    "recipient_id": "randomhash",
    "ts": 1721474736
  }
}

The Honeypot Feature

A hidden link embedded in the email body, followed only by bots. 30-minute cache window. No false positives for humans.

Recommended HTML implementation:

<a href="https://email.{domain}/{message_id}/hclick"><!-- tracking pixel --></a>

For Email Service Providers

Building bot detection in-house requires significant ongoing investment in data science, engineering, and infrastructure. The Omnivery Bot Detection API provides enterprise-grade accuracy from day one.

CriteriaBuild in-houseIntegrate Omnivery Bot Detection API
Time to first detection6-18 monthsDays
Detection accuracy at launchLow (obvious signals only)High (8+ years of data)
Bot infrastructure coverageLimited and degradingContinuously updated
Engineering costOngoingIntegration only
Data science requirementYes - ongoingNo
PII handling overheadYesNo - hashed identifiers
Compliance exposureHigherLower (EU infrastructure, GDPR-native)
Revenue modelCustomVolume-based, margin-friendly

Contact sales@omnivery.com to discuss ESP partnership arrangements, white-label options, and volume pricing.

Who Needs This

Newsletter Publishers and Media Businesses

Revenue depends on engagement metrics. beehiiv saved $14.4M in fraudulent ad spend over six months.

Email Service Providers

Remove non-human activity from the engagement data you report to customers. Included automatically for Omnivery tracking customers. Third-party ESPs supported subject to vetting.

Marketing Teams on High-Volume Transactional Programs

2FA and order confirmations pass through enterprise gateways. Contaminated data degrades ML models over time.

Ad Networks and Monetization Platforms

Botnets target click-based payouts with diverse IPs, realistic UAs, and plausible timing.

Access and Integration Requirements

  1. Domain enablement

    API returns 402 Payment Required if not enabled. Configured per domain after approval.

  2. Technical vetting

    Must be able to surface raw event data: source IP and user agent string per interaction. Platforms that obfuscate this cannot integrate.

  3. Implementation review

    For third-party ESP integrations, Omnivery reviews before enabling access.

At a Glance

  • Omnivery's Bot Detection API identifies non-human email interactions using 20+ proprietary datasets developed over 8+ years.
  • Detection categories include: security scanner clicks (Proofpoint, Mimecast, Barracuda, Microsoft Defender), Apple MPP automated opens, inbox tracking tools, and malicious botnets.
  • The API accepts up to 500 events per batch request and returns is_bot: true/false per event via webhook.
  • Minimum required fields per event: source IP (ip), user agent string (uas), unique event ID (event_id). Additional fields increase detection accuracy.
  • The honeypot endpoint captures IP and user agent of automated scanners before they reach real links, feeding a 30-minute detection cache.
  • Access requires domain enablement and technical vetting - the API returns 402 Payment Required if Bot Detection is not enabled for the requesting domain.
  • For Omnivery customers using Omnivery's own open and click tracking, bot detection is included automatically at no additional charge.
  • Third-party ESP and platform integrations are supported, subject to the technical requirement that raw event data (source IP and user agent per interaction) is available.
  • beehiiv uses the Omnivery Bot Detection API to save $14.4M in fraudulent ad spend over six months.
  • No other major transactional email provider offers an equivalent bot detection capability.
  • For ESPs, the Bot Detection API eliminates the build cost - 8+ years of proprietary data, continuous infrastructure updates, no PII sharing, no cross-customer data mixing - and can be deployed as a premium product feature in days rather than months.
  • Authentication: ov-token header. Base URL: https://zap-api.omnivery.net.

Frequently Asked Questions

What does the API actually return?

A boolean is_bot field per event - true if non-human, false if likely human. Response also returns all originally submitted fields so you can match by event_id.

Does it work with tracking data from other ESPs?

Yes, provided raw tracking events are available with source IP and user agent per interaction. If your ESP aggregates, proxies, or omits these fields, integration is not technically possible.

How does the honeypot work and is it required?

Optional but improves detection. Hidden link only bots follow. IP and UA cached for 30 minutes. Any subsequent matching event within the window is flagged immediately. One line of HTML to implement.

Can it detect Apple MPP opens?

Yes. Apple MPP routes opens through Apple's proxy infrastructure with a known IP range and user agent pattern. These are identified and flagged.

Is the batch endpoint truly asynchronous?

Yes. POST events with webhook_url, receive 202 Accepted with batch_id, results pushed to webhook when complete. Can also retrieve individual results by request_id.

Why is the single-interaction endpoint slow by design?

Minimum response time of over one second, rate limited. Prevents use as real-time classifier which would expose detection model to enumeration attacks. For volume use, use the batch endpoint.

How do I get access?

Contact sales@omnivery.com. Access requires domain enablement and brief technical review of tracking data pipeline.

Does processing event data through the API create GDPR exposure?

Designed with privacy in mind. recipient_id is recommended hashed. IPs and UAs not permanently stored associated with identifiable individuals. EU headquarters, GDPR-native architecture. DPA available at omnivery.com/legal/dpa.

Ready to Clean Your Engagement Data?

Intelligence is only as good as the data beneath it. As automation and AI make more decisions from engagement signals, telling human behavior apart from machine behavior is what keeps those decisions trustworthy. Contact the team to discuss access and confirm your tracking pipeline meets the API's technical requirements.

If you would rather start from the data than the product, The State of Email Bots 2026 carries the year-by-year series and the complete breakdown by mailbox provider. It is also available as a 10-page PDF.

Inboxing, Security, Compliance

Ready for communications infrastructure you can rely on when it matters most?