Bot Detection API
Your open rates and click rates are lying to you. Security scanners pre-click every link. Apple MPP pre-loads every pixel. Botnets inflate clicks for ad fraud. Omnivery's Bot Detection API returns a simple verdict per event: is_bot: true or is_bot: false. Used by beehiiv to save $14.4M in fraudulent ad spend over six months.
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.
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.
Newsletter ad networks are targeted by botnets: diverse IPs, legitimate user agents, realistic intervals. Invisible to simple rules.
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.
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.
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.
ov-token header. Access requires explicit enablement per domain. Contact sales@omnivery.com.
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"
}
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
}
}
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>
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.
| Criteria | Build in-house | Integrate Omnivery Bot Detection API |
|---|---|---|
| Time to first detection | 6-18 months | Days |
| Detection accuracy at launch | Low (obvious signals only) | High (8+ years of data) |
| Bot infrastructure coverage | Limited and degrading | Continuously updated |
| Engineering cost | Ongoing | Integration only |
| Data science requirement | Yes - ongoing | No |
| PII handling overhead | Yes | No - hashed identifiers |
| Compliance exposure | Higher | Lower (EU infrastructure, GDPR-native) |
| Revenue model | Custom | Volume-based, margin-friendly |
Contact sales@omnivery.com to discuss ESP partnership arrangements, white-label options, and volume pricing.
Revenue depends on engagement metrics. beehiiv saved $14.4M in fraudulent ad spend over six months.
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.
2FA and order confirmations pass through enterprise gateways. Contaminated data degrades ML models over time.
Botnets target click-based payouts with diverse IPs, realistic UAs, and plausible timing.
API returns 402 Payment Required if not enabled. Configured per domain after approval.
Must be able to surface raw event data: source IP and user agent string per interaction. Platforms that obfuscate this cannot integrate.
For third-party ESP integrations, Omnivery reviews before enabling access.
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.
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.
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.
Yes. Apple MPP routes opens through Apple's proxy infrastructure with a known IP range and user agent pattern. These are identified and flagged.
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.
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.
Contact sales@omnivery.com. Access requires domain enablement and brief technical review of tracking data pipeline.
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.
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.
Ready for communications infrastructure you can rely on when it matters most?