XOMNI: Experience Omni-Channel

Last Updated: May 05, 2016

The API provides to create new in-store metadata.

Request

[
   {
      "Key":"Key0",
      "Value":"e4404ea8-4803-4ace-80ed-6cf72617966a",
      "StoreId":2
   },
   {
      "Key":"Inventory",
      "Value":"10",
      "StoreId":1
   }
]
HTTP Method Resource URI
POST https://{tenantName}.api.xomni.com/private/catalogs/items/{id}/storemetadata

URI Parameters

Parameter Name Description Type Conditions
id The unique ID of an item. Number

Request Body Description

Parameter Name Description Type Conditions
[0..N].StoreId The unique ID of the related store. Number
[0..N].Key The key of the in-store metadata. String
[0..N].Value The value of the in-store metadata. String

Request Headers

Header Field Name Description
Content-Type
Content type of the response entity. The value of this header is always application/json.
Authorization
Access or identity token taken from oauth APIs.
Sample: Bearer dc8f1dcdbe454da8a25621839a93569337522968019e4bd7becd6e01285444da
Accept
Includes minor version header.
Sample: application/vnd.xomni.api-v4-1, */*

Response

[
   {
      "Key":"Key0",
      "Value":"e4404ea8-4803-4ace-80ed-6cf72617966a",
      "StoreId":2
   },
   {
      "Key":"Inventory",
      "Value":"10",
      "StoreId":1
   }
]

Response Body Description

Parameter Name Description Type
[0..N].StoreId The unique ID of the related store. Number
[0..N].Key The key of the in-store metadata. String
[0..N].Value The value of the in-store metadata. String

Response Headers

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

Status Codes

A successful operation returns status code 200 (OK) for POST operations. Possible response status codes are as listed below:

Status Code Description
400 (Bad Request) Specified store not found.
404 (Not Found) Metadata not found.
409 (Conflict) Specified metadata key is in use.