POST | /TaskGetById |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
TaskId | body | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Task | form | TeleportTask | No | |
ResponseStatus | form | ResponseStatus | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Id | form | string | No | |
UserName | form | string | No | |
Receiver | form | string | No | |
CreateDate | form | DateTime | No | |
StatusUpdateDate | form | DateTime | No | |
Status | form | string | No | |
Type | form | string | No | |
Body | form | string | No | |
ReceiverTeam | 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.
POST /TaskGetById HTTP/1.1
Host: wbs.e-teleport.ru
Accept: application/json
Content-Type: application/json
Content-Length: length
{"TaskId":"String"}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"Task":{"Id":"String","UserName":"String","Receiver":"String","CreateDate":"0001-01-01T00:00:00.0000000","StatusUpdateDate":"0001-01-01T00:00:00.0000000","Status":"String","Type":"String","Body":"String","ReceiverTeam":"String"},"ResponseStatus":{"ErrorCode":"String","Message":"String","StackTrace":"String","Errors":[{"ErrorCode":"String","FieldName":"String","Message":"String","Meta":{"String":"String"}}],"Meta":{"String":"String"}}}