XOMNI: Experience Omni-Channel

Last Updated: May 05, 2016

The API provides to delete in-store metadata by its key and related store.


HTTP Method Resource URI
DELETE https://{tenantName}.api.xomni.com/private/catalogs/items/{id}/storemetadata?storeId={storeId}&metadataKey={metadataKey}&metadataKeyPrefix={metadataKeyPrefix}

URI Parameters

Parameter Name Description Type Conditions
id The unique ID of an item. Number
storeId The unique ID of an store. Number
metadataKey The key for the in-store metadata String
metadataKeyPrefix In store metadata key prefix. String

Request Headers

Header Field Name Description
Access or identity token taken from oauth APIs.
Sample: Bearer dc8f1dcdbe454da8a25621839a93569337522968019e4bd7becd6e01285444da
Includes minor version header.
Sample: application/vnd.xomni.api-v4-1, */*


The response does not contain any response entity if the status is successful.

Response Headers

Header Field Name Description
Content type of the response entity. The value of this header is always application/json.

Status Codes

A successful operation returns status code 202 (Accepted) for DELETE operations. Possible response status codes are as listed below:

Status Code Description
202 (Accepted) OK
400 (Bad Request) Key and key prefix parameters cannot be sent at the same time in a in store metadata query.
404 (Not Found) Metadata not found.