HTTP 201 Created vs 429 Too Many Requests
HTTP 201 (Created) is a 2xx Success response, while 429 (Too Many Requests) is a 4xx Client Error response. 201 indicates that the request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity. In contrast, 429 means that the user has sent too many requests in a given time (rate limiting). The response should include a Retry-After header.
Descripción
The request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
Cuándo lo verás
After successfully creating a new user, post, order, or other resource via a REST API.
Cómo solucionarlo
No fix needed. Check the Location header for the URL of the new resource.
Descripción
The user has sent too many requests in a given time (rate limiting). The response should include a Retry-After header.
Cuándo lo verás
When hitting API rate limits or making too many requests too quickly.
Cómo solucionarlo
Check the Retry-After header. Implement exponential backoff. Consider caching responses.
Diferencias clave
201 is a 2xx Success response, while 429 is a 4xx Client Error response.
HTTP 201: The request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
HTTP 429: The user has sent too many requests in a given time (rate limiting). The response should include a Retry-After header.
You encounter 201 when after successfully creating a new user, post, order, or other resource via a REST API.
You encounter 429 when when hitting API rate limits or making too many requests too quickly.
Cuándo usar cada uno
For 201 (Created): No fix needed. Check the Location header for the URL of the new resource. For 429 (Too Many Requests): Check the Retry-After header. Implement exponential backoff. Consider caching responses.