XOMNI: Experience Omni-Channel

Last Updated: May 05, 2016

The API provides to create a new wishlist metadata.

Request

{
    "Key": "Key0",
    "Value": "38e92c87-1ab4-47b4-85d2-b8dcfa1f8aa6",
    "WishlistUniqueKey": "ef628ca7-b147-4396-9f61-aa2e3fec1228"
}
HTTP Method Resource URI
POST https://{tenantName}.api.xomni.com/private/pii/wishlistmetadata

Request Body Description

Parameter Name Description Type Conditions
WishlistUniqueKey The unique key of the wishlist Unknown
Required
Key Key of the metadata String
Required
Value Value of the metadata String
Required

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": "38e92c87-1ab4-47b4-85d2-b8dcfa1f8aa6",
    "WishlistUniqueKey": "ef628ca7-b147-4396-9f61-aa2e3fec1228"
}

Response Body Description

Parameter Name Description Type
WishlistUniqueKey The unique key of the wishlist Unknown
Key Key of the metadata String
Value Value of the 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
404 (Not Found) Specified wishlist not found.
409 (Conflict) Specified metadata key is in use.