---
title: API deployment · Cloudflare Zero Trust docs
description: When you choose an API deployment, email messages only reach Email Security after they have already reached a user's inbox.
lastUpdated: 2024-10-28T15:25:30.000Z
source_url:
  html: https://patricia-pcx17119-l7-overrides.preview.developers.cloudflare.com/cloudflare-one/email-security/setup/post-delivery-deployment/api/index.md
  md: https://patricia-pcx17119-l7-overrides.preview.developers.cloudflare.com/cloudflare-one/email-security/setup/post-delivery-deployment/api/
---

When you choose an API deployment, email messages only reach Email Security after they have already reached a user's inbox.

Then, through an integration with your email provider, Email Security can [auto-move messages](https://developers.cloudflare.com/cloudflare-one/email-security/auto-moves/) based on your organization's policies.

![With API deployment, messages travel through Email Security's email filter after reaching your users.](https://developers.cloudflare.com/_astro/e-sec-api-deployment-diagram.CLcGwHk2_Z9rR7F.webp)

## Benefits

When you choose API deployment, you get the following benefits:

* Easy protection for complex email architectures, without requiring any change to mailflow operations.
* Agentless deployment for Microsoft 365.

## Limitations

However, API deployment also has the following disadvantages:

* Email Security is dependent on Microsoft's Graph API, and outages will increase the message dwell time in the inbox.
* Your email provider may throttle API requests from Email Security.
* Email Security requires read and write access to mailboxes.
* Requires API support from your email provider (does not typically support on-premise providers).
* Detection rates may be lower if multiple solutions exist.
* Messages cannot be modified or quarantined.
