| POST | /machines/{MachineId}/log |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| MachineId | path | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| OrganisationId | form | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Log | form | MachineLog | No | |
| ResponseStatus | form | ResponseStatus | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | string | No | |
| MachineId | form | string | No | |
| UploadedAt | form | DateTime | No | |
| Warnings | form | int | No | |
| Errors | form | int | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Log | form | MachineLog | No | |
| ResponseStatus | form | ResponseStatus | 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 /machines/{MachineId}/log HTTP/1.1
Host: foundrystage-api-app.azurewebsites.net
Accept: application/json
Content-Type: application/json
Content-Length: length
{"machineId":"String","organisationId":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"log":{"id":"String","machineId":"String","warnings":0,"errors":0},"responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}}