424 Failed Dependency

The request failed because it depended on another action, and that action failed.

Last updated . How this page is checked.

Status code424
Status textFailed Dependency
Category4xx Client Error
Response has bodyUsually
SpecificationRFC 4918

What does 424 Failed Dependency mean?

The request failed because it depended on another action, and that action failed. 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 424?

In WebDAV, inside a multi-status response: one operation in a batch failed, so the ones that relied on it were not attempted. Some APIs use it more loosely to say that a service they depend on returned an error.

How to fix a 424 Failed Dependency

Look for the other failure. In a batch response, 424 marks the casualties, not the cause; find the entry with a different error code and fix that. Where an API uses 424 for an upstream dependency, the request itself was probably fine and is worth retrying after a pause.

Reproduce a 424 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/424 — you will see the 424 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

400 Bad Request

The server could not understand the request because it is malformed.

401 Unauthorized

The request lacks valid authentication credentials. Despite the name, this means unauthenticated.

402 Payment Required

The request cannot be processed until payment is made.

403 Forbidden

The server understood the request and knows who you are, but refuses to authorise it.

404 Not Found

The server cannot find the requested resource.

405 Method Not Allowed

The endpoint exists but does not support the HTTP method you used.

See also

  • 422 Unprocessable Entity — The syntax is valid but the content fails the server's validation rules.
  • 409 Conflict — The request conflicts with the current state of the resource.

References