Sales Layer’s REST API  supports not only reading catalog data, but also creating, updating, and deleting records using the POST, PATCH, and DELETE methods, following the OData v4.01 standard.

You can now integrate and manage Products, Variants, Categories, and Custom Entities more efficiently with our REST API.

Please note that this version has a limited scope (for example, it does not yet support bulk operations or full media asset management). However, it is fully functional and ready to be tested in real-world environments.

Deletion Behavior

When an entity (Product, Variant, Category or Custom Entity) is deleted, it will no longer be returned by the API.

This applies in both scenarios:

• When the entity is explicitly deleted.
• When the entity status is set to 'X'.

In both cases, the entity is removed from all API responses and will not appear in future queries.

Deleted entities:

• Are not returned in standard queries.
• Are not returned in incremental synchronization queries.
• Cannot be retrieved through a dedicated API endpoint.

Important Considerations for Integrations

Because deleted entities are no longer returned by the API:

• Date-based incremental synchronization (*_modify) will not include deleted entities.
• Clients cannot detect deletions directly via incremental filtering.
• There is no endpoint to retrieve deleted records.

If deletion detection is required in an external system, one of the following strategies is recommended:

1. Perform periodic full synchronization and reconcile differences.
2. Maintain a local registry of known IDs and detect missing records.
3. Implement controlled deletion workflows to prevent silent removal.

Data Consistency

Modifications performed through the API are immediately available for subsequent API requests.

There is no eventual consistency delay between write operations (POST, PATCH, DELETE) and read operations (GET).

Clients can safely query modified entities immediately after receiving a successful update response.