GET | /spytec/behaviours/device | Get list of device applied behaviors. |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Imei | query | string | Yes | The Imei of the GPS device. |
StartDate | query | DateTime | Yes | Start date to get the behaviour list. |
EndDate | query | DateTime | Yes | End date to get the behaviour list. |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Result | form | List<ListBehaviourItem> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Success | form | bool | No | |
Message | form | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Imei | form | string | No | |
CreateDate | form | string | No | |
TransmissionType | form | string | No | |
CommandStatus | form | string | No | |
TaskId | form | string | No | |
Tag | form | string | No | |
Behavior | form | string | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
GET /spytec/behaviours/device HTTP/1.1 Host: api.paylock.com Accept: application/json
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"result":[{"imei":"String","createDate":"String","transmissionType":"String","commandStatus":"String","taskId":"String","tag":"String","behavior":"String"}],"success":false,"message":"String"}