| PATCH | /serial/patch | Patch changes into entity |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Ids | query | List<Object> | No | |
| ObjectType | query | int | No | |
| PatchOperations | query | List<PatchOperation> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| PropertyName | form | string | No | |
| Value | form | Object | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Code | form | string | No | |
| ResponseStatus | form | ResponseStatus | No | |
| Result | form | Object | No | |
| IsSuccess | form | bool | 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.
PATCH /serial/patch HTTP/1.1
Host: api.chmuradokumentow.pl
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
ids:
[
{
}
],
objectType: 0,
patchOperations:
[
{
propertyName: String,
value: {}
}
]
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
code: FAIL,
responseStatus:
{
errorCode: String,
message: String,
stackTrace: String,
errors:
[
{
errorCode: String,
fieldName: String,
message: String,
meta:
{
String: String
}
}
],
meta:
{
String: String
}
},
result: {},
isSuccess: False
}