POST V1/TicketManagement.{ext}/UpdateTicketStatus

Update Ticket Status

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.Tickets
NameDescriptionTypeAdditional information
TicketID

Ticket Id

integer

None.

TicketDetailID

Ticket Detail ID

integer

None.

Source

Source

string

None.

TicketNbr

Ticket #

string

None.

Status

Status

string

None.

Maintenance

Maintenance

string

None.

RaisedBy

RaisedBy

string

None.

RaisedDate

RaisedDate

string

None.

SiteGroup

SiteGroup

string

None.

SiteNbr

Site #

string

None.

ActivationDate

Activation Date

string

None.

InActivationDate

InActivation Date

string

None.

TicketType

Ticket Type

string

None.

KeyNbr

Key #

string

None.

KeyName

Key Name

string

None.

Comments

Comments

string

None.

Ageing

Ageing

string

None.

VendorName

Vendor Name

string

None.

Request Formats

application/json, text/json

Sample:
{
  "ticketID": 1,
  "ticketDetailID": 2,
  "source": "sample string 3",
  "ticketNbr": "sample string 4",
  "status": "sample string 5",
  "maintenance": "sample string 6",
  "raisedBy": "sample string 7",
  "raisedDate": "sample string 8",
  "siteGroup": "sample string 9",
  "siteNbr": "sample string 10",
  "activationDate": "sample string 11",
  "inActivationDate": "sample string 12",
  "ticketType": "sample string 13",
  "keyNbr": "sample string 14",
  "keyName": "sample string 15",
  "comments": "sample string 16",
  "ageing": "sample string 17",
  "vendorName": "sample string 18"
}

application/xml, text/xml

Sample:
<Tickets xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/EMS.Inventory.Entities">
  <ActivationDate>sample string 11</ActivationDate>
  <Ageing>sample string 17</Ageing>
  <Comments>sample string 16</Comments>
  <InActivationDate>sample string 12</InActivationDate>
  <KeyName>sample string 15</KeyName>
  <KeyNbr>sample string 14</KeyNbr>
  <Maintenance>sample string 6</Maintenance>
  <RaisedBy>sample string 7</RaisedBy>
  <RaisedDate>sample string 8</RaisedDate>
  <SiteGroup>sample string 9</SiteGroup>
  <SiteNbr>sample string 10</SiteNbr>
  <Source>sample string 3</Source>
  <Status>sample string 5</Status>
  <TicketDetailID>2</TicketDetailID>
  <TicketID>1</TicketID>
  <TicketNbr>sample string 4</TicketNbr>
  <TicketType>sample string 13</TicketType>
  <VendorName>sample string 18</VendorName>
</Tickets>

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.