HTTP 202 – Accepted
The request has been received but not yet acted upon. Processing may not have started.
Common use case
Common in async or queue-based systems, e.g. accepting a video for transcoding or a report for background generation, where the client polls a status URL later.
Example
HTTP/1.1 202 Accepted
Location: /jobs/91a2
{"jobId":"91a2"}History
Part of HTTP/1.0 (RFC 1945, 1996), explicitly designed for "batch-oriented" processes.
Did you know?
Unlike most 2xx codes, a 202 makes no promise the operation will actually succeed - only that it was accepted for later processing.