| POST | /machines/{MachineId}/viewpoint |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| MachineId | path | string | No | |
| UploadedAt | body | DateTime | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| OrganisationId | form | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| Photo | form | Photo | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UploadedAt | form | DateTime | No | |
| ImageUrl | form | string | No | |
| ThumbnailUrl | form | string | No | |
| Id | form | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| Photo | form | Photo | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /machines/{MachineId}/viewpoint HTTP/1.1
Host: foundrystage-api-app.azurewebsites.net
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
machineId: String,
organisationId: String
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
responseStatus:
{
errorCode: String,
message: String,
stackTrace: String,
errors:
[
{
errorCode: String,
fieldName: String,
message: String,
meta:
{
String: String
}
}
],
meta:
{
String: String
}
},
photo:
{
imageUrl: String,
thumbnailUrl: String,
id: String
}
}