POST V1/Inventory.{ext}/CallToActionPersonalization

Request Information

URI Parameters

NameDescriptionTypeAdditional information
ext

Which media types are acceptable for the response, such as json/xml

If no matches are found, the content negotiator tries to match on the media type of the request body, if any. For example, if the request contains JSON data, the content negotiator looks for a JSON formatter.

string

Content-Type: application/json OR application/xml

Body Parameters

EMS.Inventory.Entities.CallToActionPersonalizationEntity
NameDescriptionTypeAdditional information
PersonalizationType

No description available

string

None.

HasAttachment

No description available

integer

None.

Origin

No description available

string

None.

Subject

No description available

string

None.

AgingInHours

No description available

string

None.

AgingInDay

No description available

string

None.

CategoryList

No description available

Collection of EMS.Inventory.Entities.CategoryEntity

None.

TagsList

No description available

Collection of EMS.Inventory.Entities.PersonalizationTags

None.

Request Formats

application/json, text/json

Sample:
{
  "categoryList": [
    {
      "categoryName": "sample string 1",
      "categoryId": 2,
      "categoryValue": "sample string 3"
    },
    {
      "categoryName": "sample string 1",
      "categoryId": 2,
      "categoryValue": "sample string 3"
    }
  ],
  "tagsList": [
    {
      "tagType": "sample string 1",
      "tagId": 2,
      "tagName": "sample string 3"
    },
    {
      "tagType": "sample string 1",
      "tagId": 2,
      "tagName": "sample string 3"
    }
  ],
  "personalizationType": "sample string 1",
  "hasAttachment": 2,
  "origin": "sample string 3",
  "subject": "sample string 4",
  "agingInHours": "sample string 5",
  "agingInDay": "sample string 6"
}

application/xml, text/xml

Sample:
<CallToActionPersonalizationEntity xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/EMS.Inventory.Entities">
  <AgingInDay>sample string 6</AgingInDay>
  <AgingInHours>sample string 5</AgingInHours>
  <CategoryList>
    <CategoryEntity>
      <CategoryId>2</CategoryId>
      <CategoryName>sample string 1</CategoryName>
      <CategoryValue>sample string 3</CategoryValue>
    </CategoryEntity>
    <CategoryEntity>
      <CategoryId>2</CategoryId>
      <CategoryName>sample string 1</CategoryName>
      <CategoryValue>sample string 3</CategoryValue>
    </CategoryEntity>
  </CategoryList>
  <HasAttachment>2</HasAttachment>
  <Origin>sample string 3</Origin>
  <PersonalizationType>sample string 1</PersonalizationType>
  <Subject>sample string 4</Subject>
  <TagsList>
    <PersonalizationTags>
      <TagId>2</TagId>
      <TagName>sample string 3</TagName>
      <TagType>sample string 1</TagType>
    </PersonalizationTags>
    <PersonalizationTags>
      <TagId>2</TagId>
      <TagName>sample string 3</TagName>
      <TagType>sample string 1</TagType>
    </PersonalizationTags>
  </TagsList>
</CallToActionPersonalizationEntity>

application/x-www-form-urlencoded

Sample:

Sample not available.

application/bson

Sample:
Binary JSON content. See http://bsonspec.org for details.

Response Information

Resource Description

EMSResponseOfEMS.Common.TransactionResults
NameDescriptionTypeAdditional information
ResponseType

No description available

string

None.

Response

No description available

EMS.Common.TransactionResults

None.

Error

No description available

EMS.Common.Error

None.

Response Formats

application/json, text/json

Sample:
{
  "responseType": "TransactionResults",
  "response": {
    "transactionResult": [
      {
        "status": "sample string 1",
        "message": "sample string 2",
        "result": "sample string 3"
      },
      {
        "status": "sample string 1",
        "message": "sample string 2",
        "result": "sample string 3"
      }
    ]
  },
  "error": {
    "errorCode": "sample string 1",
    "errorDescription": "sample string 2"
  }
}

application/bson

Sample:
Binary JSON content. See http://bsonspec.org for details.