Skip to main content
PUT
/
anomalies
/
v2
/
rs
/
resolve
Resolve anomalies internally
curl --request PUT \
  --url https://z52mnqg347.execute-api.eu-west-3.amazonaws.com/main/anomalies/v2/rs/resolve \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: <content-type>' \
  --header 'X-Session-Token: <x-session-token>' \
  --data '
{
  "anomalyIds": [
    1,
    2
  ],
  "comment": "Anomaly resolved",
  "resolvedAt": "2024-12-01T12:34:56.000Z",
  "resolvedById": 1
}
'
{
  "data": 1
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

​
Content-Type
enum<string>
required

Content type, must be "application/json".

Available options:
application/json
​
X-Session-Token
string
required

Session token used for authenticating the request.

Example:

"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VySWQiOiIxMjM0NTY3ODkwIiwic2Vzc2lvbklkIjoiYWJjZGVmMTIzNDU2IiwiaWF0IjoxNjA1MDk3ODk5LCJleHAiOjE2MDUxODQyOTl9.4XRQ1iXDyvEj5LgPZHbmTmzOZs98M3YPOzgf3MhxjaI"

Body

application/json

Details required to resolve anomalies

​
anomalyIds
number[]
required

Anomaly identifiers.

Required array length: 1 - 200 elements
Example:
[1, 2]
​
comment
string
required

Comment of the resolver.

Maximum string length: 500
Example:

"Anomaly resolved"

​
resolvedAt
required

Date of resolution of the anomaly.

Example:

"2024-12-01T12:34:56.000Z"

​
resolvedById
integer
required

Identifier of the resolver.

Example:

1

Response

200 - application/json

The anomalies have been resolved

​
data
integer
required

The number of elements concerned by the modification.

Example:

1