410 Gone

The resource was deliberately removed and will not come back.

Last updated . How this page is checked.

Status code410
Status textGone
Category4xx Client Error
Response has bodyUsually
SpecificationRFC 9110

What does 410 Gone mean?

The resource was deliberately removed and will not come back. It belongs to the 4xx Client Error class, which means the request contains bad syntax or cannot be fulfilled. Something about the request needs to change.

When do APIs return 410?

A retired API version or a permanently deleted record.

How to fix a 410 Gone

Unlike 404, this is intentional and permanent. Migrate to the replacement endpoint named in the documentation.

Reproduce a 410 response

The fastest way to understand a status code is to trigger one and read the full response. Open the API tester and send a request to https://httpbin.org/status/410 — you will see the 410 status along with every response header the server sent. Comparing those headers against a working request is often what reveals the cause.

When you are debugging a real endpoint, check the response headers as carefully as the body, and confirm you are using the right HTTP method for the operation.

Related 4xx status codes

410 Gone FAQ

What is the difference between 410 Gone and 404?

410 is a deliberate statement that the resource was removed and will not come back. 404 only says nothing was found, which may be temporary or may be a mistake in the URL.

Does 410 remove a page from search results faster than 404?

It is treated as a stronger signal that the removal is intentional, and search engines tend to drop the URL somewhat sooner, but both lead to the page being removed from the index.

Why would an API send 410 to a webhook or client?

To signal that an endpoint, API version or subscription has been retired for good. Some webhook providers also treat a 410 from your endpoint as an instruction to stop sending and remove the subscription.

See also

  • 404 Not Found — The server cannot find the requested resource.

References