# Sales Layer DAM REST API

The Sales Layer DAM REST API lets external systems work with digital assets managed by Sales Layer: images and non-image files (documents, spreadsheets, archives, and more).

Use this reference when you need to create, list, filter, retrieve, update, or delete image or file records — including registering assets from public URLs, replacing their source content or tags, and removing assets that are no longer required by your catalog workflows.

DAM operations are designed for integrations that keep media libraries, product imagery, product documentation, commerce platforms, supplier portals, and other business systems aligned with Sales Layer. For implementation guidance, review the authentication, pagination, rate limiting, and error handling guides before calling the endpoints below.


Version: 2.0.0

## Servers

Sales Layer DAM API
```
https://api2.saleslayer.com/dam
```

## Security

### ApiKey

Tenant API key. Required on every request.

Type: apiKey
In: header
Name: X-API-KEY

## Download OpenAPI description

 - [Sales Layer DAM REST API](https://docs.api.saleslayer.com/_bundle/apis/dam-v2.0.yaml)

## Files

 - [GET /files](https://docs.api.saleslayer.com/apis/dam-v2.0/files/paths/~1files/get.md): Returns a paginated collection of the tenant's non-image files (documents, spreadsheets, archives, …), filtered and sorted using OData query options (`$filter`, `$orderby`, `$top`, `$skip`). ## Authen
 - [POST /files](https://docs.api.saleslayer.com/apis/dam-v2.0/files/paths/~1files/post.md): Registers a new file from a publicly accessible URL, optionally tagging it. The file is fetched, checked against the supported formats and the size limit, and stored. ## Authentication Requires a vali
 - [GET /files({reference})](https://docs.api.saleslayer.com/apis/dam-v2.0/files/paths/~1files(%7Breference%7D)/get.md): In DAM, files are identified by their filename (`reference`), which is unique per tenant. Use this endpoint to retrieve a specific file when you already know its filename. ## Authentication Requires a
 - [PATCH /files({reference})](https://docs.api.saleslayer.com/apis/dam-v2.0/files/paths/~1files(%7Breference%7D)/patch.md): Partially updates an existing file identified by its filename (`reference`), which is unique per tenant — substitute its contents via a new `url` and/or replace its `tags`. At least one of these field
 - [DELETE /files({reference})](https://docs.api.saleslayer.com/apis/dam-v2.0/files/paths/~1files(%7Breference%7D)/delete.md): Deletes a file by its filename (`reference`), which is unique per tenant. ## Authentication Requires a valid API key in the `X-API-KEY` header. ## Example ``` DELETE /files(product-datasheet.pdf) X-A
## Images

 - [GET /images](https://docs.api.saleslayer.com/apis/dam-v2.0/images/paths/~1images/get.md): Returns a paginated collection of the tenant's images, filtered and sorted using OData query options (`$filter`, `$orderby`, `$top`, `$skip`). ## Authentication Requires a valid API key in the `X-API-
 - [POST /images](https://docs.api.saleslayer.com/apis/dam-v2.0/images/paths/~1images/post.md): Registers a new image from a publicly accessible URL, optionally tagging it. The image is downloaded, validated against the supported formats and size limits, and processed asynchronously in the backg
 - [GET /images({reference})](https://docs.api.saleslayer.com/apis/dam-v2.0/images/paths/~1images(%7Breference%7D)/get.md): In DAM, images are identified by their filename (`reference`), which is unique per tenant. Use this endpoint to retrieve a specific image when you already know its filename. ## Authentication Requires
 - [PATCH /images({reference})](https://docs.api.saleslayer.com/apis/dam-v2.0/images/paths/~1images(%7Breference%7D)/patch.md): Partially updates an existing image identified by its filename (`reference`), which is unique per tenant — substitute its file via a new `url` and/or replace its `tags`. At least one of these fields m
 - [DELETE /images({reference})](https://docs.api.saleslayer.com/apis/dam-v2.0/images/paths/~1images(%7Breference%7D)/delete.md): Deletes an image by its filename (`reference`), which is unique per tenant. ## Authentication Requires a valid API key in the `X-API-KEY` header. ## Example ``` DELETE /images(product-main-front.jpg)