Create Attribute Set
Sales Layer Catalog REST API (2.0.0)
The Sales Layer Catalog REST API provides programmatic access to the catalog data managed in Sales Layer.
Use this reference to retrieve, filter, create, update, or delete products, variants, categories, attribute sets, custom entities, metadata, and changelog records. These endpoints support synchronization, enrichment, publishing, reporting, and other integration workflows across ecommerce platforms, ERPs, marketplaces, DAM systems, supplier systems, and internal tools.
Start with metadata endpoints when your integration needs to discover available fields and relationships, use pagination and filtering for large reads, and rely on changelogs for incremental synchronization whenever possible.
Download OpenAPI description
Attribute Sets
Operations
- GET /AttributeSets
- GET /AttributeSets({attributeSetIdentifier})
- GET /AttributeSets({attributeSetIdentifier})/Products
- GET /AttributeSets/$metadata
Request
Returns all attribute sets defined for the tenant, each including its name, identifier, and form layout configuration for Products and Variants (ProductLayout, VariantLayout).
Authentication
Requires a valid API key in the X-API-KEY header.
Response
200 OK — GetAttributeSetsResponse containing the list of attribute sets.
Example
Request:
GET /v2/AttributeSets HTTP/1.1
X-API-KEY: your-api-key-here
Response:
HTTP/1.1 200 OK
Content-Type: application/json
Layout Validation
A layout may contain any subset of the tenant's valid attributes — you do not need to include all of them. Attributes omitted from the layout simply do not appear in the form for this attribute set; they are not removed from the tenant.
Required attributes
These attributes must always be present in their respective layout:
| Layout | Required attribute IDs |
|---|---|
productLayout |
typ_id, prod_ref, prod_title, cat_ref, prod_stat, prod_description, prod_image, prod_tags |
variantLayout |
frmt_stat, prod_ref, frmt_ref, frmt_tags |
Example Request Payload
{"name": "Electronics"}
Create Attribute Set
POST /v2/AttributeSets
Creates a new attribute set for the tenant from the supplied name and optional Product and Variant form layouts, returning the created attribute set and a Location header pointing to it.
Request Body
| Field | Required | Description |
|---|---|---|
name |
✅ Yes | Unique name for the attribute set within the tenant. |
productLayout |
❌ No | Form layout for Products. Defaults to the standard layout when omitted. |
variantLayout |
❌ No | Form layout for Variants. When omitted, no Variant layout is created (it can be added later via PATCH). |
Example
Request:
POST /v2/AttributeSets HTTP/1.1
X-API-KEY: your-api-key-here
Content-Type: application/json
{ "name": "Electronics" }
Response:
HTTP/1.1 201 Created
Location: /v2/AttributeSets(7)
Delete Attribute Set
DELETE /v2/AttributeSets({id})
Deletes the attribute set identified by id (a positive integer). The tenant's default attribute set cannot be deleted.
Example Request
DELETE /v2/AttributeSets(7)?deleteAssociatedProductsAndVariants=false HTTP/1.1
X-API-KEY: your-api-key-here
Response:
HTTP/1.1 200 OK
Content-Type: application/json
Error Responses
- 401 Unauthorized — Missing or invalid tenant identifier.
- 500 Internal Server Error — Unexpected technical error.
Summary
Hence, the Cleaning output focuses strictly on retrieving the attribute set data through insightful API endpoint usage and validation of different request and response structures.