HTTP status codes / 4xx — Client errors
410 Gone
It existed, it was removed on purpose, it is not coming back.
What it means
A deliberate, permanent absence — stronger than 404. Useful for deprecated API versions and deleted content; search engines de-index 410s faster.
Common causes
- Deliberately removed resource (deprecated API version, deleted content)
- Expired one-time links
How to debug it
Stop retrying. Check the changelog/deprecation notes for the replacement endpoint.
Server-side note: Stop retrying — 410 is intentional and permanent. Check the changelog for the replacement.
The fastest way to pin down a 410 is to reproduce the exact request and inspect what actually went over the wire — status, headers, timing and body, without your app code in the way. That is what an API client is for; ReqPad does it from your phone, with every request saved to history.
Related codes
400 Bad Request · 401 Unauthorized · 402 Payment Required · 403 Forbidden · 404 Not Found · 405 Method Not Allowed — or the full reference.
Reproduce that 410 in 10 seconds.
Build the request, send it, read status + headers + timing — on your iPhone. Free to start.