409
Conflict
Client errors (4xx)·RFC 9110
HTTP 409 Conflict is a Client errors (4xx) status code. The request conflicts with the current state of the resource.
What 409 means
The request conflicts with the current state of the resource.
Common in concurrent edits (version mismatch) or when creating a resource that already exists.
Client errors (4xx)
The request contains an error from the client — bad syntax, missing auth or a wrong URL.
Other 4xx codes
400Bad Request401Unauthorized402Payment Required403Forbidden404Not Found405Method Not Allowed406Not Acceptable407Proxy Authentication Required408Request Timeout410Gone411Length Required412Precondition Failed413Content Too Large414URI Too Long415Unsupported Media Type416Range Not Satisfiable417Expectation Failed418I'm a teapot421Misdirected Request422Unprocessable Content423Locked424Failed Dependency425Too Early426Upgrade Required428Precondition Required429Too Many Requests431Request Header Fields Too Large451Unavailable For Legal Reasons
FAQ — 409
What does HTTP 409 mean?
409 Conflict: The request conflicts with the current state of the resource. Common in concurrent edits (version mismatch) or when creating a resource that already exists.
Which class does status code 409 belong to?
409 is a Client errors (4xx) code. The request contains an error from the client — bad syntax, missing auth or a wrong URL.
Where is the 409 code defined?
Status code 409 is defined in RFC 9110 and is part of the IANA HTTP Status Code Registry.