# DAM REST API overview

The DAM REST API is used to integrate external systems with Sales Layer digital asset management capabilities.

It focuses on image resources. An integration can list images, retrieve individual images by reference, and delete images when they are no longer needed.
It can also register new images from public URLs and partially update existing images by replacing the source URL and/or tags.

Use this API when an external system needs to keep product images, media references, or asset metadata aligned with Sales Layer.

## Main capabilities

| Capability | What it is used for |
|  --- | --- |
| Create images | Register a new image from a publicly accessible HTTP or HTTPS URL and optionally assign tags. |
| List and filter images | Retrieve image records and narrow results by supported query parameters. |
| Retrieve a single image | Get the full record for a specific image by its reference (filename). |
| Update images | Replace an image source and/or replace tags for an existing image reference. |
| Delete images | Remove an image resource by its reference (filename). |


## Endpoint summary

| Method | Path | Functional description |
|  --- | --- | --- |
| `GET` | `/dam/images` | Retrieves image records. Use this endpoint to search, filter, sort, and paginate DAM images. |
| `POST` | `/dam/images` | Creates an image from a publicly accessible URL. The image is processed asynchronously after creation. |
| `GET` | `/dam/images({reference})` | Retrieves the full record for a single image by its reference (the image filename, unique per tenant). |
| `PATCH` | `/dam/images({reference})` | Partially updates an image by replacing its source URL and/or tags. The replacement URL must keep the same filename as the current reference. |
| `DELETE` | `/dam/images({reference})` | Deletes an image resource by its reference (filename) when it can be safely removed. |


## Typical integration scenarios

Use the DAM REST API to:

* Retrieve image records to verify processing status or asset availability.
* Register externally hosted image files so they can be managed in Sales Layer.
* Replace image content or tags for an existing image reference.
* Remove obsolete images as part of a controlled cleanup workflow.


## Before implementing

Make sure your integration:

* Sends a valid API key in the `X-API-KEY` header.
* Uses pagination when reading lists of images.
* Uses image references (filenames) as identifiers when retrieving or deleting individual images.
* Uses public HTTP or HTTPS URLs when creating or replacing images.
* Handles temporary processing states when creating, updating, or deleting images (a `409` response means the image conflicts with the current processing state).
* Applies retry and rate limiting behavior as described in [Rate limiting](/guides/rate-limiting).
* Reviews [DAM error details](/guides/errors) for image-specific failure cases.


## Technical reference

Use the [DAM REST API v2.0 OpenAPI reference](/apis/dam-v2.0) for request parameters, schemas, examples, and status codes.

## Related pages

* [Quickstart](/guides/quickstart)
* [Pagination and filtering](/guides/pagination-and-filtering)
* [Error responses](/guides/error-responses)
* [DAM REST API v2.0 OpenAPI reference](/apis/dam-v2.0)