Retrieve a list of historic values for the specified mapping.
POST/history/mapping/:mapping
Retrieves a list of historic values for mappings specified with the given id values. Id values are named by entity (e.g. 'testcase_id', 'testrun_id'). The entity type needs to support history tracking.
Request
Path Parameters
The name of the mapping or colon-separated entity names
- application/json
Body
required
id
object
Entity ids for mapped entities, e.g. testcase_id
Responses
- 200
- 4XX
- 5XX
Returns 'MappingHistoryResult'
- application/json
- Schema
- Example (from schema)
Schema
Array [
]
Timestamp of first historic entry
Timestamp of last historic entry
data
object[]
required
List of requested entity ids and a list of historical values (for each entity)
The entity ids of the mapping
The list of historical mapping values, one for each step, with 'valid_from' and 'valid_to' interval properties
{
"from": "2024-07-29T15:51:28.071Z",
"to": "2024-07-29T15:51:28.071Z",
"data": [
{
"ids": {},
"values": [
{}
]
}
]
}
The request failed because invalid request parameters or data were supplied or access was denied.
- application/json
- Schema
- Example (from schema)
Schema
The error code describing the general error category.
API_INVALID_INPUT_DATA
The HTTP status code.
The actual error message describing the error in more detail.
The request id for following up on specific errors.
{
"code": "API_INVALID_INPUT_DATA",
"status": 0,
"message": "string",
"reqid": "string"
}
The request failed because an error occurred during processing of the request.
- application/json
- Schema
- Example (from schema)
Schema
The error code describing the general error category.
API_INVALID_INPUT_DATA
The HTTP status code.
The actual error message describing the error in more detail.
The request id for following up on specific errors.
{
"code": "API_INVALID_INPUT_DATA",
"status": 0,
"message": "string",
"reqid": "string"
}