Skip to the content

202 Accepted

The request was accepted and will be processed later. The response can't say yet how that will turn out.

Class
2xx Successful. The request was received, understood and accepted.
Defined in
RFC 9110

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

When a server sends it

When the work takes too long to wait for: generating a report, sending a batch of mail, converting a video. The server puts the job in a queue and answers at once.

What to do with it

Don't treat it as success, because the job can still fail. A well-behaved service says in the body or in a Location header where the progress can be followed, and you ask there until it reports a result.

If you build such a service, give the client that address, and let it answer 200 with the state of the job while it runs.

Not to be confused with

201 CreatedThe new resource exists already.
200 OKThe work is done.
102 ProcessingInterim: the client is kept waiting on the same request.

How Google treats it

Google's crawler waits a limited time for the content after a 202 and then goes on with whatever it has received.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12