Use this quickstart to make a first authenticated request and confirm that your integration can reach Sales Layer REST APIs.
Before you start, make sure you have:
- A Sales Layer account with REST API access.
- A valid API key.
- A tool that can send HTTPS requests, such as cURL, Postman, or an integration runtime.
All requests in this documentation use the current API base URL:
https://api2.saleslayer.comSend the API key in the X-API-KEY header.
X-API-KEY: YOUR_API_KEYDo not include API keys in browser code, public repositories, screenshots, or customer-facing logs.
Start with a small DAM request to verify authentication, connectivity, and response handling.
curl -X GET 'https://api2.saleslayer.com/dam/image?$top=10' \
-H 'X-API-KEY: YOUR_API_KEY'This request returns up to 10 image records when the API key has access to the DAM API.
A successful request returns an HTTP 200 OK response with a JSON payload.
If the request fails:
| Status code | What to check first |
|---|---|
400 | Query parameter syntax and supported values. |
401 | The X-API-KEY header is present and contains the correct key. |
404 | The endpoint path and resource identifier are correct. |
409 | The resource is not locked by a temporary processing state. Applies to write operations only, for example DELETE /dam/image/{id}. Not returned by GET /dam/image. |
500 | Retry only with bounded backoff and log the failure for investigation. |
For Catalog integrations, use metadata before building dynamic requests.
curl -X GET 'https://api2.saleslayer.com/catalog/rest/Catalog/$metadata' \
-H 'X-API-KEY: YOUR_API_KEY'Metadata responses help integrations understand available fields, resource structures, and relationships before requesting or writing catalog data.