XOMNI: Experience Omni-Channel

Last Updated: February 19, 2016

The API allows a client application to import a wishlist which is pointed by OmniTicket to current PII User’s wishlists.

Request

{
    "OmniTicket": "bda570b0-cf86-4c86-830c-ac9445faf208",
    "GpsLocation": {
        "Longitude": 35.6885,
        "Latitude": -67.44767
    }
}
HTTP Method Resource URI
POST https://{tenantName}.api.xomni.com/pii/wishlist/import

Request Body Description

Parameter Name Description Type Conditions
OmniTicket A single-use ticket for a wishlist. String
Required
GpsLocation.Longitude Longitude value of the location. Number
GpsLocation.Latitude Latitude value of the location. Number

Request Headers

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

Response

{
    "Data": {
        "WishlistUniqueKey": "bda570b0-cf86-4c86-830c-ac9445faf208"
    }
}

Response Body Description

Parameter Name Description Type
Data.WishlistUniqueKey Imported wishlist unique key. 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) Invalid OmniTicket