[Deprecated]: v9.0

get

/ec-query-svc/rest/v9.0/studies/{studyId}/{mode}/queryDetails

Deprecated: Use latest version instead. Compared to v8.0, this v9.0 endpoint preserves query-details filtering and response semantics while aligning with v9 metadata handling. This benefits users by enabling predictable upgrades for query-details consumers.

Request

Path Parameters

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Successful operation.
Body ()
Root Schema : schema
Type: array
Show Source
Nested Schema : QueryDetailsDTOv9Resp
Type: object
Show Source
Nested Schema : comments
Type: array
A list of comments associated with the query
Show Source
Nested Schema : studyRoles
Type: array
Study-role assignments associated with the query. Each entry supplies the role UUID and display name.
Show Source
Example:
[
    {
        "studyRoleId":"68C35A92894A4ABCB2E2F6008E4402DB",
        "studyRoleName":"CRA"
    }
]
Nested Schema : CommentDetailsDTO
Type: object
A list of comments associated with the query
Show Source
  • Text recorded for this query interaction or state transition.
    Example: Please verify the value.
  • Allowed Values: [ "Candidate", "Opened", "Answered", "Closed", "Deleted" ]
    Lifecycle state at this interaction, not necessarily the current query state. Candidate is awaiting triage; Opened awaits a response; Answered awaits review; Closed is resolved; Deleted is removed.
    Example: Opened
  • DisplayUserDto
    User details including name, username, and email address.
  • Captured value associated with this interaction; can contain a JSON-encoded value/label array or be null.
    Example: [{"value":"4","label":"Caucasian"}]
  • Effective timestamp of this history interaction, in ISO-8601 format.
    Example: 2026-01-01T10:00:00Z
Nested Schema : DisplayUserDto
Type: object
User details including name, username, and email address.
Show Source
Example:
{
    "id":"00000000000000000000000000000003",
    "userName":"autocalc"
}
Nested Schema : QueryStudyRoleDTOv6
Type: object
Show Source
Examples

400 Response

Request validation failed due to missing, invalid, or inconsistent request data.
Body ()
Root Schema : Response DTO
Type: object
Base envelope returned by Query APIs. Use the status field to determine whether result or errorData is populated.
Show Source
Nested Schema : Error details DTO
Type: object
Standard structure used to describe errors returned by Query APIs.
Show Source
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: object
Result payload returned when status equals success.
Example:
{
    "opened":3,
    "answered":1,
    "closed":2
}
Nested Schema : QueryRestErrorDetail
Type: object
Read Only: true
Context object returned when additional error metadata is available.
Show Source
  • Client-facing guidance that clarifies how to resolve or retry the request.
    Example: Retry request after verifying the study mode.
  • Unique identifier that can be supplied to Oracle Support when troubleshooting.
    Example: 3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a
  • 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.
Body ()
Root Schema : Response DTO
Type: object
Base envelope returned by Query APIs. Use the status field to determine whether result or errorData is populated.
Show Source
Nested Schema : Error details DTO
Type: object
Standard structure used to describe errors returned by Query APIs.
Show Source
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: object
Result payload returned when status equals success.
Example:
{
    "opened":3,
    "answered":1,
    "closed":2
}
Nested Schema : QueryRestErrorDetail
Type: object
Read Only: true
Context object returned when additional error metadata is available.
Show Source
  • Client-facing guidance that clarifies how to resolve or retry the request.
    Example: Retry request after verifying the study mode.
  • Unique identifier that can be supplied to Oracle Support when troubleshooting.
    Example: 3b3b8f31-87a3-4dd2-8b9d-21d0c93ef27a
  • 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

Back to Top