Get list of users to send notifications to
get
/ec-notifications-svc/rest/v1.0/studies/{studyId}/{mode}/{rightname}
Retrieves a list of the users who have the right associated with receiving given notifications.
Request
Path Parameters
-
mode(required): string
Mode of the study. Accepts active, test, or training.
-
rightname(required): string
Name of the right associated with receiving notifications. Valid values are taken from authorization service.
-
studyId(required): string
ID of the study.
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 NotificationUserDto
Represents a user associated with a notification privilege (right). Includes user identification, notification privilege, name, email, and subscription status.
Nested Schema : NotificationUserDto
Type:
objectRepresents a user associated with a notification privilege (right). Includes user identification, notification privilege, name, email, and subscription status.
Show Source
-
privilege: string
(none)
The name of the notification right or privilege that this user is associated with.Example:
SITE_NOTIFY -
subscription: string
(none)
'YES' if the user has subscribed to the notification indicated by 'privilege', otherwise 'NO'.Example:
YES -
userEmailAddress: string
(email)
Email address of the user as recorded in AUTH_USERS.Example:
sunita.smith@clinicalone.com -
userId: string
(uuid)
Hexadecimal string representing the UUID of the user authorized for this privilege.
-
userName: string
(none)
User???s full name, as given_name + family_name from AUTH_USERS, separated by a space.Example:
Alex Smith
400 Response
Bad request.
Root Schema : ErrorResponseData
Type:
objectStructure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
-
details: string
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 -
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