HTTP 202 Accepted vs 429 Too Many Requests
HTTP 202 (Accepted) is a 2xx Success response, while 429 (Too Many Requests) is a 4xx Client Error response. 202 indicates that the request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon. 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 has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon.
Cuándo lo verás
For async operations like batch jobs, email sending, or background tasks that take time to complete.
Cómo solucionarlo
Poll the provided status URL or wait for a callback/webhook.
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
202 is a 2xx Success response, while 429 is a 4xx Client Error response.
HTTP 202: The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon.
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 202 when for async operations like batch jobs, email sending, or background tasks that take time to complete.
You encounter 429 when when hitting API rate limits or making too many requests too quickly.
Cuándo usar cada uno
For 202 (Accepted): Poll the provided status URL or wait for a callback/webhook. For 429 (Too Many Requests): Check the Retry-After header. Implement exponential backoff. Consider caching responses.