Skip to main content

Error Codes

The Seddi API uses standard HTTP status codes. This page explains what each code means in context and what to do when you encounter one.

Status code reference​

200 OK​

The request was successful. The response body contains the requested data.

204 No Content​

Used internally for CORS preflight responses. You should not encounter this in normal API usage.

400 Bad Request​

The request was malformed or contained invalid parameters.

Common causes:

  • Missing a required field in the request body (e.g. brand, number in the image generator)
  • Missing a required query parameter on Style Data list endpoints (e.g. brand and number on colorways)
  • A parameter value in an unexpected format

What to do: Check your request body and parameters against the API Reference.

401 Unauthorized​

The API key is missing or invalid.

Common causes:

  • The x-api-key header was not included
  • The key value contains extra whitespace
  • The key has been revoked

What to do: Verify your API key. See Authentication for details.

404 Not Found​

No style matched brand, number, color, and size on the product-image or techpack generators.

What to do: Check those four values against Style Data. The response body uses error:

{
  "error": "Style not found"
}

429 Too Many Requests​

You have exceeded the rate limit of 1,000 requests per minute.

What to do: Implement exponential backoff and retry. See Rate Limits.

500 Internal Server Error​

An unexpected error occurred on the Seddi backend.

What to do: Retry the request. If the error persists, contact support@seddi.com with the request details and timestamp.

504 Gateway Timeout​

The request timed out, typically because the backend was scaling up under load.

What to do: This is transient. Retry after a few seconds. See Rate Limits for a retry pattern.

Error response format​

Error responses are returned as JSON where available:

{
  "error": "Missing or invalid API key"
}
info

Not all error responses include a JSON body — some (like 504) may return an empty body or a gateway-level HTML page. Always check the HTTP status code first.