POST api/device/EnableDevice?ApplicationKey={ApplicationKey}&APIKey={APIKey}&DeviceID={DeviceID}

This method provides the capability to re-enable a device that has been discarded.

Request Information

URI Parameters

NameDescriptionTypeAdditional Information
ApplicationKey

The application identity issued by an authorized publisher of Traxia services. This identity is unique and generated one-time during registration.

string

Required

APIKey

Secret key issued to be challenged as identity verification.

string

Required

DeviceID

Unique code to identify a device that connects to the Traxia system, such as IMEI.

string

None

Body Parameters

In the Traxia 6, parameter body consists of parameters and values, the parameters used in this case are lookup and updateby.

APIParameters
NameDescriptionTypeAdditional Information
Parameters

New technique from Traxia to simplify filling data in body parameter by just input key value and the system will retrieve the available information.

Collection of Pair of string [key] and string [value]

Required

Request Formats

application/json, text/json

Sample:
// enable Device parameter query offers optional filters using key-value pair such as following
{
    "Parameters": [ 
    { 
        "Key": "lookup", 
        "Value": "SIEMENS-002" // mandatory, your Deviceid, integer   
    },
    { 
        "Key": "updateby", 
        "Value": "care@dit.co.id" //mandatory, the responsible email, string   
    } 
  ] 
}

application/xml, text/xml

Sample:
<APIParameters xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Traxia.Common">
  <Parameters xmlns:d2p1="http://schemas.datacontract.org/2004/07/System.Collections.Generic">
    <d2p1:KeyValuePairOfstringstring>
      <d2p1:key>sample string 1</d2p1:key>
      <d2p1:value>sample string 2</d2p1:value>
    </d2p1:KeyValuePairOfstringstring>
    <d2p1:KeyValuePairOfstringstring>
      <d2p1:key>sample string 1</d2p1:key>
      <d2p1:value>sample string 2</d2p1:value>
    </d2p1:KeyValuePairOfstringstring>
  </Parameters>
</APIParameters>

multipart/form-data

Sample:
<APIParameters xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Traxia.Common"><Parameters xmlns:d2p1="http://schemas.datacontract.org/2004/07/System.Collections.Generic"><d2p1:KeyValuePairOfstringstring><d2p1:key>sample string 1</d2p1:key><d2p1:value>sample string 2</d2p1:value></d2p1:KeyValuePairOfstringstring><d2p1:KeyValuePairOfstringstring><d2p1:key>sample string 1</d2p1:key><d2p1:value>sample string 2</d2p1:value></d2p1:KeyValuePairOfstringstring></Parameters></APIParameters>

application/x-www-form-urlencoded

Sample:

Sample not available.

Response Information

Resource Description

BaseResponse
NameDescriptionTypeAdditional Information
Acknowledge

Acknowledgement of API request format, whether you are submitting the requested parameter in a proper format.

Acknowledge

None

ResponseCode

Indicates the result of your API service process. Negative results may have different code indicators depending on their failure type.

ResponseCode

None

ResponseMessage

Negative API process results may have additional information in text to explain the failure reasons.

string

None

Data

Data provide a universal object response model transformed into JSON compatible format. You will need to recognize the type of returned object model of each of your request. For more information about object class model, please consult our object class library documentation.

Object

None

Latency

integer

None

Response Formats

application/json, text/json

Sample:
// Succesful result of enable Device 
{
    "Acknowledge": 1, 
    "ResponseCode": 200, 
    "ResponseMessage": "Request was succesfully performed.", 
    "Data": null
}