Error Handling
ThredUp API follows standard HTTP status code conventions to indicate the outcome of each request.
2xx Success: The request was successfully received, understood, and processed.4xx Client Error: The request was invalid or cannot be processed due to client-side issues, such as missing or invalid parameters, authentication errors, or referencing a non-existent resource.5xx Server Error: An unexpected error occurred on ThredUp’s side. These are typically temporary and should be retried with exponential backoff if appropriate.
Use the response code and message to identify the cause of failure and determine whether a correction, retry, or support inquiry is needed.
| Status Code | Category | Description |
|---|---|---|
200 OK |
Success | The request was successfully processed. |
201 Created |
Success | A resource was successfully created. |
400 Bad Request |
Client Error | The request is malformed or missing required parameters. |
401 Unauthorized |
Client Error | Authentication failed or is missing. |
403 Forbidden |
Client Error | The client is authenticated but not authorized to perform this action. |
404 Not Found |
Client Error | The requested resource could not be found. |
422 Unprocessable Entity |
Client Error | The request was well-formed but semantically invalid (e.g., failed validation). |
429 Too Many Requests |
Client Error | Rate limit exceeded, retry after some time, ideally with an exponential backoff. |
500 Internal Server Error |
Server Error | Something went wrong on ThredUp’s side. |
503 Service Unavailable |
Server Error | The server is temporarily unavailable (e.g., due to maintenance or overload). |