V1.0

get

/ec-dc-svc/rest/v1.0/studies/{studyId}/{mode}/enrollmentsettings

Fetch all persisted enrollment settings for a given study and mode. Returns a response containing an array of EnrollmentSetting objects, each representing the settings for a group.

Request

Path Parameters

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Success: Returns an array of persisted enrollment settings for the specified study and mode.
Body ()
Root Schema : EnrollmentSetting
Type: object
Represents the persisted enrollment setting for a study group.
Show Source
  • Minimum Length: 0
    Maximum Length: 2048
    Comment regarding the last change made to the entity.
    Example: Imported via migration tool.
  • Brief description of the enrollment setting.
    Example: Phase 1 - First cohort group
  • Indicates if the enrollment setting is enabled.
    Example: true
  • Title of the group receiving this setting.
    Example: Cohort A
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) for the enrollment setting.
    Example: 1BC29B36F5D64B1B95F4BDBBCEA481BE
  • Notification threshold for approaching subject limit.
    Example: 80
  • Minimum Length: 1
    Maximum Length: 16
    Operation type on the record, can have values CREATED, MODIFIED or REMOVED
    Example: REMOVED
  • Minimum Length: 0
    Maximum Length: 255
    Reason for the entity creation or latest modification.
    Example: Initial import.
  • Maximum number of subjects allowed in this group.
    Example: 100
  • The timestamp marking the beginning of the validity period for this record version within the system.
    Example: 2023-01-01T09:00:00Z
Examples

400 Response

Bad request.
Body ()
Root Schema : DcsResponse
Type: object
Show Source
Nested Schema : ErrorResponseData
Type: object
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
  • details
    Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
  • Application or business-specific error code representing the error type.
    Example: REPT_401
  • Human-readable error message describing the failure or issue.
    Example: Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type: object
Nested Schema : details
Type: object
Detailed 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
Back to Top