What Is a 410 Response? #

A 410 Gone HTTP response signals that the requested resource no longer exists and will not return. DMSI Webhooks treats a 410 response as a permanent signal that the endpoint URL is no longer valid.

Automatic Behavior on 410 #

When a delivery receives a 410 Gone response:

1. The delivery is immediately marked as permanently failed
2. The endpoint status is changed from active to disabled
3. All future deliveries to this endpoint are stopped
4. An admin notification email is sent immediately (regardless of notification frequency setting)

How to Recover #

Option A: Re-activate the Endpoint #

If the endpoint URL is now valid again (e.g., it was temporarily unavailable):

1. Go to DDLS > Webhooks > Endpoints
2. Click Edit on the disabled endpoint
3. Change Status to active
4. Click Save

Deliveries will resume for the next event that fires.

Option B: Update the URL and Re-activate #

If the endpoint moved to a new URL:

1. Edit the endpoint
2. Update the URL field
3. Change Status to active
4. Send a test delivery to verify the new URL is reachable
5. Save

Option C: Delete and Recreate #

If the endpoint is no longer needed, delete it. All associated subscription records and log entries are deleted with it (cascade delete).

Preventing False 410 Disables #

If your server returns 410 for reasons other than permanent removal (e.g., a configuration error), update your server logic to return a different error code (500, 503) for transient failures. A 410 response should only be returned when an endpoint is intentionally decommissioned.

Related Topics #

• Endpoint Settings Reference
• Delivery Status Reference
• Troubleshooting Failed Deliveries