# Current limitations

This page summarizes current documented limitations that integrations should consider when using Sales Layer REST APIs.

The OpenAPI reference remains the source of truth for the exact parameters and operations supported by each endpoint.

## Query limitations

The migrated documentation identifies the following query limitations:

| Limitation | Practical impact |
|  --- | --- |
| No filtering on nested resource properties | Apply `$filter` to properties of the root resource returned by the endpoint. |
| No ordering by multiple properties | Use a single supported property in `$orderby` unless the endpoint reference explicitly documents otherwise. |
| No selecting properties from embedded resources | Use `$select` for properties of the requested resource. Do not assume it can select fields inside expanded collections. |
| No expanding nested collections | Use `$expand` only for supported embedded collections directly exposed by the resource. |
| Maximum page size of 100 items | Design pagination loops around a maximum of 100 records per page unless an endpoint documents a stricter limit. |


## API-specific notes

DAM list operations currently document `$filter`, `$orderby`, `$top`, and `$skip`.

Catalog list operations document a broader set of query parameters, including `$select`, `$expand`, `$filter`, `$orderby`, `$top`, `$skip`, and `$skipToken`, depending on the endpoint.

## DAM asset creation

`POST /images` and `POST /files` require a filename of at most **255 characters, extension excluded**. The filename comes from the final segment of the source URL path. Longer names return `400 Bad Request` with `File name exceeds maximum length of 255 characters`.

`PATCH /images({reference})` and `PATCH /files({reference})` keep the existing asset name; the creation limit does not apply to the replacement URL's filename. Other URL, size, format, and tag restrictions still apply as documented for the operation.

DAM does not follow redirects when checking source URLs for `POST` or `PATCH`. Supply the direct image or file URL. A `3xx` response is rejected with `400 Bad Request`, such as `URL is not accessible. HTTP status: 302 Found`.

All DAM operations are **Beta**. Review [REST API Evolution and Compatibility Policy](/rest-api-evolution-and-compatibility-policy) and the [Changelog](/changelog) when maintaining integrations.

## Recommended approach

To avoid unsupported requests:

* Use metadata endpoints to discover Catalog resource fields and relationships.
* Check the OpenAPI reference for the exact parameters supported by the endpoint.
* Test query expressions with small page sizes before using them in batch jobs.
* Keep filtering, sorting, and field selection focused on the root resource.
* Avoid building integrations that depend on undocumented nested filtering or nested expansion behavior.


## Related pages

* [Pagination and filtering](/guides/pagination-and-filtering)
* [Select](/guides/select)
* [Filter](/guides/filter)
* [Orderby](/guides/orderby)
* [Expand](/guides/expand)
* [Page size limits](/guides/page-size-limits)