Add Point Values
POST {{baseUrl}}/points/:pointId/values?overwrite=false
Point value ingestion is exposed for evaluation purposes until the new subscription is released by January 2024.
Push 1 to 100 values for given point in a batch.
Only one point value per millisecond will be stored. pointValues are dropped if there are timestamp conflicts, i.e. if a point value with the same timestamp already exists. Example with following pointValues: 1. 2022-07-11T11:11:30.333 2. 2022-07-11T11:11:30.222 3. 2022-07-11T11:11:30.333 4. 2022-07-11T11:11:30.444
The first is accepted (it's the first for time 30.333
).
The second is also accepted.
The third is dropped because it's the same timestamp as the first.
The fourth is accepted again.
The indices of dropped pointValues are listed in the response (0-based), in this example there is one conflict with index 2
.
If there is no conflict status 204 is returned instead of 202.
Note: Use query parameter 'overwrite=true' to force overwriting of conflicting values.
Request Params
| Key | Datatype | Required | Description |
|---|---|---|---|
overwrite | boolean | The value and attributes of a pointValue with the provided timestamp (including the milliseconds) will only be overwritten when this parameter is set to true. | |
| The parameter is ignored when no pointValue with this timestamp exists. The parameter is applied to all pointValues in the payload. | |||
| If set to true the existing value and attributes are completely replaced by the new value and attributes from the payload. | |||
Request Body
{"data"=>[{"type"=>"<string>", "attributes"=>{"timestamp"=>"<dateTime>", "value"=>"<string>", "qualityOfValue"=>"<integer>"}}, {"type"=>"<string>", "attributes"=>{"timestamp"=>"<dateTime>", "value"=>"<string>", "qualityOfValue"=>"<integer>"}}]}
HEADERS
| Key | Datatype | Required | Description |
|---|---|---|---|
Content-Type | string | ||
Accept | string |