Skip to content
RU Sign In
RU
← All Status Codes
409
Client Error

409 Conflict

The request conflicts with the current state of the server.

Definition (RFC 9110)

HTTP status code 409 409 Conflict is defined in RFC 9110 (HTTP Semantics), Section 15.5.10 — the current authoritative specification for HTTP semantics, published June 2022, which obsoletes the older RFC 7231 and RFC 2616.

Description

The 409 Conflict status code indicates that the request could not be completed due to a conflict with the current state of the target resource. This is commonly used in situations where the user might resolve the conflict and resubmit the request.

Common Causes

  • Concurrent edits to the same resource
  • Duplicate resource creation
  • Version conflict (optimistic locking)

How to Fix

  • Fetch the latest version and retry
  • Implement conflict resolution logic
  • Use ETags for conditional updates

Check your website's HTTP status code

Check now →

Related Status Codes

400
400 Bad Request
The server cannot process the request due to malformed syntax.
 401
401 Unauthorized
Authentication is required and has failed or not been provided.
 402
402 Payment Required
402 Payment Required — code reserved for future use, but currently used by some APIs to signal "payment needed".
 403
403 Forbidden
The server understood the request but refuses to authorize it.
 404
404 Not Found
404 Not Found — the requested URL does not exist on the server. The most common client-error; signals search engines to remove the page from index.
 405
405 Method Not Allowed
The HTTP method used is not allowed for this resource.

Related guides

Longer-form reading on this topic from the knowledge base.

Automate this check

Set up continuous monitoring and get an alert when something breaks. No manual runs to remember.

Start free

Start monitoring for free

Sign up and get access to API, monitoring and notifications

Create Account API Documentation