HTTP Status Codes Cheat Sheet/Create success codes

Typical responses when creating resources.

Section: Common API Response Patterns

Create success codes

text
text
201 Created
202 Accepted
204 No Content
Explanation

`201` commonly indicates a resource was created, while `202` means the request was accepted for asynchronous processing and may not be completed yet.

Learn the surrounding workflow

Compare similar commands or jump into common fixes when this command is part of a bigger troubleshooting path.

Related commands

Same sheet · prioritizing Common API Response Patterns
GET success codes
Typical success responses for reads.
OpenIn sheettextsame section
Authentication and authorization codes
The most common auth-related status codes.
OpenIn sheettextsame section
Rate limiting and overload codes
Responses commonly used when a client must back off.
OpenIn sheettextsame section
HTTP status code classes
Understand the five categories of HTTP responses.
OpenIn sheettext1 tag match
Debug status codes in the right order
A quick flow for deciding where a problem lives.
OpenIn sheettext1 tag match
Check headers and status with curl
Inspect the response line and headers only.
OpenIn sheetbash1 tag match