DELETE
/
api
/
v2
/
endpoints
/
{id}
DELETE https://inbound.new/api/v2/endpoints/{id}

{
  "message": "Endpoint deleted successfully",
  "cleanup": {
    "emailAddressesUpdated": 3,
    "emailAddresses": [
      "alerts@example.com",
      "support@example.com",
      "notifications@example.com"
    ],
    "domainsUpdated": 1,
    "domains": [
      "example.com"
    ],
    "groupEmailsDeleted": 2,
    "deliveriesDeleted": 145
  }
}

​
Overview

Permanently delete an endpoint and clean up all associated resources. This action cannot be undone. The endpoint will be removed and all associated email addresses and domains will be updated accordingly. 
DELETE https://inbound.new/api/v2/endpoints/{id}

​
Authentication

​
Authorization
string
required
Bearer token for API authentication. Format: Bearer YOUR_API_KEY

​
Path Parameters

​
id
string
required
The unique identifier of the endpoint to delete.

​
Response

{
  "message": "Endpoint deleted successfully",
  "cleanup": {
    "emailAddressesUpdated": 3,
    "emailAddresses": [
      "alerts@example.com",
      "support@example.com",
      "notifications@example.com"
    ],
    "domainsUpdated": 1,
    "domains": [
      "example.com"
    ],
    "groupEmailsDeleted": 2,
    "deliveriesDeleted": 145
  }
}

​
Response Fields

​
message
string
Confirmation message that the endpoint was deleted successfully.
​
cleanup
object
Details about the cleanup operations performed during deletion.

​
Examples

​
Delete Webhook Endpoint

curl -X DELETE "https://inbound.new/api/v2/endpoints/ep_abc123" \
  -H "Authorization: Bearer your_api_key"

​
Delete Email Group Endpoint

curl -X DELETE "https://inbound.new/api/v2/endpoints/ep_def456" \
  -H "Authorization: Bearer your_api_key"

​
Error Responses

​
What Happens During Deletion

1

Email Address Cleanup

All email addresses that route to this endpoint are updated to “store only” mode. They will continue to receive emails but won’t be forwarded or sent to webhooks.
2

Domain Catch-All Updates

Any domains using this endpoint for catch-all routing will have their catch-all configuration removed.
3

Email Group Cleanup

If this is an email group endpoint, all email addresses in the group are deleted from the group table.
4

Delivery History Cleanup

All delivery history records associated with this endpoint are permanently deleted.
5

Endpoint Deletion

Finally, the endpoint itself is deleted from the system.

​
Important Considerations

This action cannot be undone. Once an endpoint is deleted, all its configuration and delivery history are permanently lost.
Email addresses affected by the deletion will continue to receive emails in “store only” mode. You can later configure them to route to a different endpoint.
Before deleting an endpoint, consider disabling it first using the update endpoint to test the impact on your email routing.

​
Impact on Email Routing

Email Addresses

Emails will be stored but not forwarded or sent to webhooks

Catch-All Domains

Unknown emails to these domains will be stored but not routed

​
Best Practices

​
Before Deletion

  1. Review dependencies - Check which email addresses and domains use this endpoint
  2. Test impact - Disable the endpoint first to see the impact
  3. Backup configuration - Save endpoint configuration if you might need to recreate it
  4. Plan migration - Set up replacement endpoints for affected email addresses

​
After Deletion

  1. Update email addresses - Configure affected email addresses to route to new endpoints
  2. Update catch-all domains - Configure new catch-all endpoints for affected domains
  3. Monitor email flow - Ensure emails are being routed correctly to new endpoints
  4. Clean up unused resources - Remove any other resources that depended on this endpoint

​
Cleanup Response Breakdown

The cleanup response helps you understand what was affected:
Shows which email addresses were set to “store only” mode and need to be reconfigured with new endpoints.

​
Recovery Options