| POST | /DocumentGetList |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UserName | body | string | Yes | |
| DocumentType | body | DocumentType? | No | |
| UpdateDate | body | string | No |
| failure | |
| warrantyService | |
| additionalWorks | |
| maintenance |
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 /DocumentGetList HTTP/1.1
Host: s10.tdfkm.ru
Accept: application/json
Content-Type: application/json
Content-Length: length
{"userName":"String","documentType":"failure","updateDate":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"documents":[{"id":"String","uid":"String","number":"String","createDateUtc":"0001-01-01T00:00:00.0000000","lastUpdateDateUtc":"0001-01-01T00:00:00.0000000","kindOfMaintenance":"String","commentSMS":"String","address":"String","maintenancePlanName":"String","maintenanceDate":"String","documentStatus":"String","mainTask":false,"deadlineDateUtc":"0001-01-01T00:00:00.0000000"}],"responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}}