Ravi Sir's Cards › AWS
201 vs 202
This revision card explains 201 vs 202. It starts from the need that always returning 200 hides whether work finished or was queued. It describes 201 = created sync; 202 = accepted for async processing. The how-to section notes sync create , then 201; queue accepted , then 202 + Location/id. An example on the card is omar Hassan teaches status codes before fancy frameworks.
Read card text
What this card says
Why do we need it?
Always returning 200 hides whether work finished or was queued.
What is it?
201 = created sync; 202 = accepted for async processing.
202 Accepted
How to do it
Sync create → 201; queue accepted → 202 + Location/id.
Example
Omar Hassan teaches status codes before fancy frameworks.