ListingForBulkUpsertByFacility: Allows sending different listing information for the same tenantArticleId for multiple facilities.
The listing version must be sent for an update; otherwise, a new listing is created. If a listing with the same tenantArticleId already exists, the entire update batch fails.
Searching for the listing version
Before updating existing listings, their current version must be retrieved. This can be done by searching for the listings. The bulk API can then be used to update multiple listings across various facilities simultaneously.
The following example demonstrates searching for all listings with tenantArticleId4711 to retrieve their current versions.
It might be necessary to iterate over multiple pages to get all listings with the corresponding tenantArticleId. More information can be found under Pagination.
The search returns the complete listings.
Updating with ListingForBulkUpsertBySelector
To update multiple listings, send a PUT request to the following endpoint with the JSON body:
Each object in the selector array specifies a listing in a particular facility by its tenantArticleId and current version. A single batch can update up to 25 listings. This can be achieved by providing 25 selectors for one listing, or through multiple listings with their respective selectors. The endpoint returns the updated listings and a summary of the operations.
This is an all-or-nothing behavior. If one listing insert fails, all others will fail as well.
Updating with ListingForBulkUpsertByFacility
To update multiple listings, send a PUT request to the following endpoint with the JSON body:
The endpoint returns the updated listings and a summary of the operations.
This is an all-or-nothing behavior. If one listing insert fails, all others will fail as well.