GET | /Distribution/MobileUsers/{MobileUserId}/Tasks | ||
---|---|---|---|
GET | /Distribution/MobileUsers/Tasks/{TaskId} | ||
GET | /Distribution/MobileUsers/Tasks |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
TaskId | path | int? | No | |
MobileUserId | path | int? | No | |
DDate | query | DateTime? | No | |
TermDate | query | DateTime? | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Result | form | List<MobileUserTask> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Id | form | int | No | |
MobileUserId | form | int | No | |
BranchId | form | int | No | |
Ddate | form | DateTime | No | |
TermDate | form | DateTime | No | |
Task | form | string | No | |
Done | form | bool | 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 /Distribution/MobileUsers/{MobileUserId}/Tasks HTTP/1.1 Host: apex.nikoratrade.ge Accept: application/json
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"Result":[{"Id":0,"MobileUserId":0,"BranchId":0,"Ddate":"\/Date(-62135596800000-0000)\/","TermDate":"\/Date(-62135596800000-0000)\/","Task":"String","Done":false}]}