DAM error details

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

For cross-API status code guidance, see 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:

{
  "type": "https://api2.saleslayer.com/errors/validation",
  "title": "Bad Request",
  "status": 400,
  "detail": "The request is invalid.",
  "instance": "/images(product-main-front.jpg)"
}

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 /images

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

GET /images({reference})

• Invalid API key

DELETE /images({reference})

• Invalid image reference (filename)
• 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:

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 /images({reference})

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

Troubleshooting checklist

Before retrying a failed request, verify:

• The X-API-KEY header is present and valid
• The endpoint path is correct
• The image reference (filename) is correct when using DELETE
• Query parameters are supported and correctly formatted