Remove a forwarding address from a site

remove_site_email_forward_address

Takes one address off the forwarding addresses of a site, so mail sent to the site stops reaching it at once.

POST /v1/remove_site_email_forward_addressScopeconfig:writeDestructive

The address can be added again later, and then needs a new confirmation unless it is confirmed at once. When it was the last confirmed address, mail sent to the site is dropped from then on, and the tool tells the client to say so. It also tells the client to confirm with you first.

It needs the Delete projects permission. See Forwarding addresses.

Request

Call it with a POST to https://api.modulify.ai/v1/remove_site_email_forward_address, sending the inputs below as a JSON object. The token needs the config:write scope.

This method is marked destructive: it deletes or overwrites data. Check the inputs before you call it, and send an Idempotency-Key header whenever you might retry it.

curl -X POST https://api.modulify.ai/v1/remove_site_email_forward_address \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"projectId":"PROJECT_ID","addressId":"ADDRESS_ID"}'

Over MCP, the same method is the remove_site_email_forward_address tool.

Inputs

Input	Type	Required	Description
`projectId`	string	Yes	The site id.
`addressId`	string	Yes	The id of the forwarding address, from `forwarding.recipients` in `get_site_email_settings`.

Response

Every call answers with the JSON envelope of success, message, data, code and version. data holds the result described above, and on a method that returns a total, count carries it. The response headers carry the call's X-Request-Id and what is left of your per-minute budget in X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Errors explains every status code a call can answer with.