# DAM error details

This page lists DAM REST API error details for image operations.

For cross-API status code guidance, see [Error responses](/guides/error-responses).

The DAM REST API uses standard HTTP status codes to indicate whether a request succeeded or failed.

When an operation fails, first check:

* The `X-API-KEY` header
* Path and query parameter values
* Whether the target image exists
* Whether the image is currently being processed


## Error response format

Most error responses use a JSON problem-details structure.

Example:


```json
{
  "type": "https://api2.saleslayer.com/errors/validation",
  "title": "Bad Request",
  "status": 400,
  "detail": "The request is invalid.",
  "instance": "/image/123"
}
```

The OpenAPI specification defines a `ProblemDetails` schema with these fields:

* `type`
* `title`
* `status`
* `detail`
* `instance`


## 400 Bad Request

The request is syntactically valid HTTP, but the API cannot process it because one or more values are invalid.

Common causes:

### GET `/image`

* Invalid `$filter` syntax
* Unsupported field in `$orderby`
* Invalid pagination values such as `$top` or `$skip`
* Invalid API key


### DELETE `/image/{id}`

* Invalid image identifier
* Invalid request


## 401 Unauthorized

The request does not include a valid API key.

Typical causes:

* Missing `X-API-KEY` header
* Empty API key value
* Invalid API key


Example:


```http
X-API-KEY: YOUR_API_KEY
```

## 404 Not Found

The requested image does not exist or cannot be found for the current tenant.

This can happen when:

* The image identifier is wrong
* The image has already been deleted
* The image does not belong to the current tenant context


## 409 Conflict

The operation cannot be completed because the image is currently being processed.

In the DAM API this status is relevant for:

* `DELETE /image/{id}`


This usually means the image is temporarily locked by an active processing workflow. Retry later.

## 500 Internal Server Error

The server encountered an unexpected error while processing the request.

Typical causes include:

* Network connectivity issues
* Storage service unavailable
* Database errors


A `500` response usually indicates a temporary or server-side problem rather than a client-side validation issue.

## Endpoint summary

| Endpoint | Possible error codes |
|  --- | --- |
| `GET /image` | `400`, `401` |
| `DELETE /image/{id}` | `400`, `401`, `404`, `409`, `500` |


## Troubleshooting checklist

Before retrying a failed request, verify:

* The `X-API-KEY` header is present and valid
* The endpoint path is correct
* The image `id` is valid when using `DELETE`
* Query parameters are supported and correctly formatted


## Related pages

* [Introduction](/guides/introduction)
* [Authentication](/guides/authentication)
* [Rate limiting](/guides/rate-limiting)
* [Error responses](/guides/error-responses)
* [API reference overview](/apis)