[Deprecated]: v9.0
put
/ec-query-svc/rest/v9.0/studies/{studyId}/{mode}/queries/{queryId}/close
Deprecated: Compared to v8.0, this v9 endpoint adds visit date validation and returns the richer QueryV9Response payload with property metadata. This improves user integration reliability.
Request
Path Parameters
-
mode(required): string
Study mode. Allowed values: test (testing sandbox), training (training environment), and active (production).Example:
test -
queryId(required): string
ID of the query to close.Example:
AE33A9096BF548BBB29A96E399E9FBBB -
studyId(required): string
Clinical One study identifier formatted as a 32 to 36 character GUID.Example:
A1B23C45D67E89F123456789ABCDEF12
Supported Media Types
- application/json
Root Schema : QueryDTO Version 9
Type:
objectTitle:
QueryDTO Version 9Information for creating/editing query
Show Source
-
dataElementId: string
(uuid)
Data element unique GUID.
-
discrepancyId: integer
(int64)
Discrepancy identifier sourced from Data Capture. Negative values are rejected.Example:
123456789 -
eventId: string
(uuid)
Event unique GUID.
-
eventInstanceNumber: number
(int64)
Sequence number (0, 1, 2, ...) of the repeating event. Negative values are rejected.Example:
0 -
formId: string
(uuid)
Form unique GUID.
-
formInstanceNumber: number
(int64)
Sequence number (0, 1, 2, ...) of the repeating form. Negative values are rejected.Example:
0 -
id: string
(uuid)
Query unique identifier. Value must be a 32 to 36 character hexadecimal GUID.
-
itemId: string
(uuid)
Item unique GUID.
-
objectVersionNumber: number
(int64)
Sequence number (0, 1, 2, ...) of object version. Negative values are rejected.Example:
0 -
propertyName: string
Property name associated with the query when Data Capture properties are involved. Example: visit.Example:
visit -
propertyType: string
Allowed Values:
[ "visit", "visitStartDate" ]Property type classification. Allowed values: visit (query anchored to visit details), visitStartDate (query anchored to the visit start date).Example:visit -
queryComment: string
Minimum Length:
1Maximum Length:2048Query comments captured during open, candidate, or close operations.Example:Query comment example here.. -
repeatFormNumber: integer
(int64)
Repeat form sequence number. Negative values are rejected.Example:
1 -
siteId: string
(uuid)
Site unique GUID.
-
studyRoles: array
studyRoles
List of study role identifiers assigned to the query.
-
studyVersionStart: string
(date-time)
Data element version start timestamp in ISO-8601 format.Example:
2026-01-15T10:05:30Z -
subjectId: string
(uuid)
Subject unique GUID.
-
userDisplayName: string
First and last name of the query creator or last modifier.Example:
John Doe
Example:
{\n \"queryComment\": \"Visit date clarification required.\",\n \"subjectId\": \"762744769B0E4E40B6A74691179BC578\",\n \"dataElementId\": \"583A45DD0A1C46F88D7842D76CAF9A59\",\n \"formId\": \"680E0FB01F1B4CCB990C333563FAEE80\",\n \"siteId\": \"CB9BBB0767114F599FE75616223D6665\",\n \"eventId\": \"3B95322B15144E4397B30305EB33E871\",\n \"eventInstanceNumber\": 0,\n \"formInstanceNumber\": 0,\n \"itemId\": \"42738D18833E45C29D9CDEABBB2247FE\",\n \"studyRoles\": [\"6AF54DB79B764662B685D68C52AB0B84\"],\n \"discrepancyId\": 123456789,\n \"propertyName\": \"visit\",\n \"propertyType\": \"visitStartDate\",\n \"userDisplayName\": \"Jane QueryAuthor\"\n}Nested Schema : studyRoles
Type:
arrayList of study role identifiers assigned to the query.
Show Source
Example:
[
"6AF54DB79B764662B685D68C52AB0B84",
"6AF54DB79B764662B685D68C52AB0B84"
]Examples
Back to Top
Response
Supported Media Types
- application/json
200 Response
Successful operation.
Root Schema : Response DTO
Type:
objectBase envelope returned by Query APIs. Use the status field to determine whether result or errorData is populated.
Show Source
-
errorData: object
Error details DTO
Standard structure used to describe errors returned by Query APIs.
-
result: object
result
Result payload returned when status equals success.
-
status: string
Read Only:
trueAllowed Values:[ "success", "failed" ]Overall execution status. Value is success when result is populated and failed when errorData is returned.Example:success -
version: string
Read Only:
trueSemantic version of the response envelope.Example:1
Example:
{\n \"status\": \"success\",\n \"result\": {\n \"id\": \"AE33A9096BF548BBB29A96E399E9FBBB\",\n \"state\": \"Answered\"\n },\n \"errorData\": null,\n \"version\": \"1\"\n}Nested Schema : Error details DTO
Type:
objectStandard structure used to describe errors returned by Query APIs.
Show Source
-
details: object
QueryRestErrorDetail
Read Only:
trueContext object returned when additional error metadata is available. -
errorCode: string
Read Only:
trueMachine-readable error code that identifies the failure.Example:QRY-5000 -
errorMessage: string
Read Only:
trueHuman-readable explanation describing why the request failed.Example:Unexpected server error.
Example:
{
"errorCode":"QRY-5000",
"errorMessage":"Unexpected server error.",
"details":{
"requestId":"3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a",
"supportCode":"QRY-5000",
"hint":"Retry request after verifying the study mode."
}
}Nested Schema : result
Type:
objectResult payload returned when status equals success.
Example:
{
"opened":3,
"answered":1,
"closed":2
}Nested Schema : QueryRestErrorDetail
Type:
objectRead Only:
trueContext object returned when additional error metadata is available.
Show Source
-
hint: string
Client-facing guidance that clarifies how to resolve or retry the request.Example:
Retry request after verifying the study mode. -
requestId: string
Unique identifier that can be supplied to Oracle Support when troubleshooting.Example:
3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a -
supportCode: string
Support or incident code associated with the error source.Example:
QRY-5000
Example:
{
"requestId":"3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a",
"supportCode":"QRY-5000",
"hint":"Retry request"
}Examples
400 Response
Request validation failed due to missing, invalid, or inconsistent request data.
Root Schema : Response DTO
Type:
objectBase envelope returned by Query APIs. Use the status field to determine whether result or errorData is populated.
Show Source
-
errorData: object
Error details DTO
Standard structure used to describe errors returned by Query APIs.
-
result: object
result
Result payload returned when status equals success.
-
status: string
Read Only:
trueAllowed Values:[ "success", "failed" ]Overall execution status. Value is success when result is populated and failed when errorData is returned.Example:success -
version: string
Read Only:
trueSemantic version of the response envelope.Example:1
Example:
{\n \"status\": \"success\",\n \"result\": {\n \"id\": \"AE33A9096BF548BBB29A96E399E9FBBB\",\n \"state\": \"Answered\"\n },\n \"errorData\": null,\n \"version\": \"1\"\n}Nested Schema : Error details DTO
Type:
objectStandard structure used to describe errors returned by Query APIs.
Show Source
-
details: object
QueryRestErrorDetail
Read Only:
trueContext object returned when additional error metadata is available. -
errorCode: string
Read Only:
trueMachine-readable error code that identifies the failure.Example:QRY-5000 -
errorMessage: string
Read Only:
trueHuman-readable explanation describing why the request failed.Example:Unexpected server error.
Example:
{
"errorCode":"QRY-5000",
"errorMessage":"Unexpected server error.",
"details":{
"requestId":"3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a",
"supportCode":"QRY-5000",
"hint":"Retry request after verifying the study mode."
}
}Nested Schema : result
Type:
objectResult payload returned when status equals success.
Example:
{
"opened":3,
"answered":1,
"closed":2
}Nested Schema : QueryRestErrorDetail
Type:
objectRead Only:
trueContext object returned when additional error metadata is available.
Show Source
-
hint: string
Client-facing guidance that clarifies how to resolve or retry the request.Example:
Retry request after verifying the study mode. -
requestId: string
Unique identifier that can be supplied to Oracle Support when troubleshooting.Example:
3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a -
supportCode: string
Support or incident code associated with the error source.Example:
QRY-5000
Example:
{
"requestId":"3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a",
"supportCode":"QRY-5000",
"hint":"Retry request"
}Examples
404 Response
The query could not be found.
Root Schema : Response DTO
Type:
objectBase envelope returned by Query APIs. Use the status field to determine whether result or errorData is populated.
Show Source
-
errorData: object
Error details DTO
Standard structure used to describe errors returned by Query APIs.
-
result: object
result
Result payload returned when status equals success.
-
status: string
Read Only:
trueAllowed Values:[ "success", "failed" ]Overall execution status. Value is success when result is populated and failed when errorData is returned.Example:success -
version: string
Read Only:
trueSemantic version of the response envelope.Example:1
Example:
{\n \"status\": \"success\",\n \"result\": {\n \"id\": \"AE33A9096BF548BBB29A96E399E9FBBB\",\n \"state\": \"Answered\"\n },\n \"errorData\": null,\n \"version\": \"1\"\n}Nested Schema : Error details DTO
Type:
objectStandard structure used to describe errors returned by Query APIs.
Show Source
-
details: object
QueryRestErrorDetail
Read Only:
trueContext object returned when additional error metadata is available. -
errorCode: string
Read Only:
trueMachine-readable error code that identifies the failure.Example:QRY-5000 -
errorMessage: string
Read Only:
trueHuman-readable explanation describing why the request failed.Example:Unexpected server error.
Example:
{
"errorCode":"QRY-5000",
"errorMessage":"Unexpected server error.",
"details":{
"requestId":"3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a",
"supportCode":"QRY-5000",
"hint":"Retry request after verifying the study mode."
}
}Nested Schema : result
Type:
objectResult payload returned when status equals success.
Example:
{
"opened":3,
"answered":1,
"closed":2
}Nested Schema : QueryRestErrorDetail
Type:
objectRead Only:
trueContext object returned when additional error metadata is available.
Show Source
-
hint: string
Client-facing guidance that clarifies how to resolve or retry the request.Example:
Retry request after verifying the study mode. -
requestId: string
Unique identifier that can be supplied to Oracle Support when troubleshooting.Example:
3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a -
supportCode: string
Support or incident code associated with the error source.Example:
QRY-5000
Example:
{
"requestId":"3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a",
"supportCode":"QRY-5000",
"hint":"Retry request"
}Examples