v1.0
get
/ec-dataintegration-svc/rest/v1.0/studies/{studyId}/{mode}/properties/history
Retrieves Data Capture properties history.
Request
Path Parameters
-
mode(required): string
Mode of the study, accepts: test, active, or training.Example:
active -
studyId(required): string(uuid)
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.Example:
A1B2C3D4E5F647839ABCDEF012345678
Query Parameters
-
limit: integer(int32)
Minimum Value:
0Maximum number of records to display per page.Example:100 -
offset: integer(int32)
Minimum Value:
0An order number to specify with which object you want to start retrieving result. If provided, you also need to specify a value for the limit parameter.Example:0 -
propertyId: string(uuid)
Unique Identifier (UUID, 32-character uppercase hexadecimal string) of the property.Example:
2A5E92F1C2D54DDA9F1C0A9E7B3C2D1A
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/json
200 Response
Success
Root Schema : schema
Type:
Show Source
array-
Array of:
object PropertyDto1
Property Dto having fields which specify the unique property Id
Nested Schema : PropertyDto1
Type:
objectProperty Dto having fields which specify the unique property Id
Show Source
-
comment: string
Additional comments for the property update.Example:
Configured during study setup -
id: string
Unique identifier for the property record.Example:
1BC29B36F5D64B1B95F4BDBBCEA481BE -
objectVersionNumber: number
Object version number used for concurrency control.Example:
1 -
operationType: string
Operation type on the record, can have values CREATED, MODIFIED or REMOVEDExample:
MODIFIED -
propertyAttr: string
Additional attribute or data type for the property.Example:
{} -
propertyKey: string
Unique key name of the property.Example:
1BC29B36F5D64B1B95F4BDBBCEA481BE -
propertyStatus: string
Status of the property.Example:
1 -
propertyType: string
Type/category of the property.Example:
CODING_PROPERTY -
propertyValue: string
Value configured for the property.Example:
UTC -
reason: string
Reason for the change in property value.Example:
Initial configuration -
softwareVersionNumber: number
Software version number used when the record was generated.Example:
300 -
userId: string
Unique Identifier (UUID, 32-character uppercase hexadecimal string) of the userExample:
699EF3745FC545589F186D2198F3C65E -
versionEnd: string
(date-time)
The end date until which the data is applicable or valid.Example:
2023-01-01T10:00:00Z -
versionStart: string
(date-time)
Record version start timestamp.Example:
2023-01-01T09:00:00Z
Examples
400 Response
Bad_Request
Root Schema : RestResponse
Type:
Show Source
object-
errorData: object
ErrorResponseData
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
-
result: object
result
-
status: string
-
version: integer
(int32)
Nested Schema : ErrorResponseData
Type:
objectStructure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
-
details: object
details
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
-
errorCode: string
Application or business-specific error code representing the error type.Example:
REPT_401 -
errorMessage: string
Human-readable error message describing the failure or issue.Example:
Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type:
objectNested Schema : details
Type:
objectDetailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
Example:
User role is missing required permission REPORTING_VIEW. Field: userId