202 Accepted

The 202 Accepted status code indicates that the request has been queued for processing, but final results are not yet available.

A 202 response is noncommittal; there may be an error or other problem that prevents the operation from completing successfully. However, there is currently no standard way of correlating the final outcome to an HTTP status code.

There is currently no standard for waiting on asynchronous operations, see Asynchronous Operations in HTTP for suggestions on how to implement this feature.

Writing responses (servers)

Applications may find the 202 status code useful for any situation where they need to respond to a request, but needs to be noncommittal with how the operation will eventually resolve.

Use of this status may be affected by the respond-async and wait tokens in the Prefer header.

If the operation can be considered completed instead, see 201 (Created).

Services may also consider 303 (See Other) to redirect the client to a page that contains information about the current status of the request. Servers may wish to use 303 by default (for Web browser support), unless you know a 202 status code is desired (for example, because of the presence of the respond-async preference).

Reading responses (clients)

Clients may want to handle 202 similar to 201 (Created), except that 202 does not imply the request has completed, and there may be errors yet to come.

Clients following an application-specific use may follow the directions for that use.

Implementations

Overview table

Name

202

Message

202 Accepted

Description

The requested operation has been queued.

Specification

RFC 7231: HTTP/1.1 Semantics and Content §6.3.3. 202 Accepted

Example

HTTP/1.1 202 Accepted