# API reference overview

Sales Layer REST APIs let external systems read and manage information from Sales Layer using HTTPS requests and JSON payloads.

This section contains two types of content:

* API overviews, written for readers who need to understand what each API is for before working with endpoints.
* OpenAPI references, generated from OpenAPI specifications and intended for implementation details.


## Available APIs

| API | Maturity | Purpose |
|  --- | --- | --- |
| [DAM REST API](/apis/dam) | **Beta** | Manage digital asset resources — images and non-image files — including listing, retrieval, search, creation, updates, and deletion. |
| [Catalog REST API](/apis/catalog) | **Stable** | Work with catalog resources such as products, variants, categories, attribute sets, custom entities, metadata, and changelogs. |


See the [REST API Evolution and Compatibility Policy](/rest-api-evolution-and-compatibility-policy) for the guarantees of each maturity level. Catalog metadata endpoints are part of the current Catalog reference.

The `v2.0` reference labels and dated Swagger filenames identify the current documentation sources. A new source file or changelog entry does not imply a new independently selectable API version. Numeric changelog identifiers identify documentation publications and are not product versions.

## Choosing where to start

Start with the API overview if you are new to Sales Layer APIs or need to understand what a set of endpoints does from a business or integration perspective.

Go directly to the OpenAPI reference when you already know the endpoint you need and want to inspect parameters, schemas, examples, and status codes.

## Related pages

* [Quickstart](/guides/quickstart)
* [Authentication](/guides/authentication)
* [Catalog REST API overview](/apis/catalog)
* [DAM REST API overview](/apis/dam)
* [Sales Layer MCP Server](/mcp-server)