XOMNI: Experience Omni-Channel

Last Updated: May 05, 2016

This API asks for a social platform tokens and saves it to the PII User data store for the social platform which is given through the {socialPlatformName} parameter. Token naming conventions might be different for different platforms. For facebook, request body must contain "access_token" key and value. XOMNI API returns extended token key value pair with the same key name. For twitter, request body must contain "oauth_token" and "oauth_verifier" key/value pairs. XOMNI API returns access token and secret with "oauth_token", "oauth_token_secret" key naming.

Request

{"access_token":"AAADHTenCKrkBAOZCLcNfxaTzC32D4ZCLcK6SKPKZCRFmjLaCvV9gGBu5qmxBtEIOgw69HCKBcHXevZB1CVLikNcZByYbXPZAX5simVZBSA8PQZDZD"}
HTTP Method Resource URI
POST https://{tenantName}.api.xomni.com/social/token/{socialPlatformName}

Request Body Description

The social API platform access token to be saved for the current PII context.

Possible values for available platforms

Value Description
facebook The key used for the Facebook social platform.
twitter The key used for the Twitter social platform.

Request Headers

Header Field Name Description
Content-Type
Content type of the response entity. The value of this header is always application/json.
PIIToken
Includes the base64-encoded “Personally Identifiable Information” data.
Sample: dXNlcm5hbWU6SW5uQXBwc1VzZXI7cGFzc3dvcmQ6SW5uQXBwc1Bhc3M=
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

{  
   "Data":{  
      "access_token":"CAAGVVMuW7ZBIBAJFMFs2e2tYlhK9HiaUbFhzYHUA2nn2O1MHBfFZC7MbZAM2zN621HCEZAoZBjfmeizVLgaAH4o59VNFwsXUkeZAFqomKzQZA0JCWavUuJ5epv447HT9dPwa0bKNe31WHKCA4zAHKrNMjK99H9izAFIxxflgehWyjdysI3HNzvI8ApL6KkUX5IZD"
   }
}

Response Body Description

Parameter Name Description Type
Data The social API platform access tokens to be saved for the current PII context. 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) Access token must be not null or token extending error.
400 (Bad Request) Configuration of this social platform is invalid. Please check social platform settings in tenant settings.
404 (Not Found) The value for the {socialPlatformName} key is not in the list of possible values.