Use $select to choose which properties of a resource should be included in a response.
This parameter is supported by selected Catalog API endpoints. It is not documented in the current DAM OpenAPI specification.
Use $select when an integration only needs a subset of fields.
This can reduce response size, simplify processing, and make synchronization jobs easier to debug.
$select=PROPERTY_NAME,ANOTHER_PROPERTY_NAMEExample:
GET https://api2.saleslayer.com/catalog/rest/Catalog/Products?$select=prod_ref,prod_titleThe property names must match the resource metadata exposed by the Catalog API.
Use metadata endpoints to inspect available fields before building dynamic requests:
GET https://api2.saleslayer.com/catalog/rest/Catalog/Products/$metadata
GET https://api2.saleslayer.com/catalog/rest/Catalog/Categories/$metadata
GET https://api2.saleslayer.com/catalog/rest/Catalog/Variants/$metadata{
"value": [
{
"prod_ref": "PROD-001",
"prod_title": {
"en": "Example product"
}
}
],
"@count": 1,
"@readLink": "https://api2.saleslayer.com/catalog/rest/Catalog/Products?$select=prod_ref,prod_title"
}$selectapplies to properties of the requested resource.- Use exact property names from metadata.
- Combine
$selectwith$filter,$orderby, and pagination when supported by the endpoint. - If a field is missing from the response, verify that it was included in
$selectand is available for the resource.