[Deprecated]: V1.0

get

/ec-notifications-svc/rest/v1.0/studies/{studyId}/{mode}/notificationsbroadcast/{id}

Deprecated: Retrieves notification broadcast details by notification broadcast ID.

Request

Path Parameters
  • ID of the notification to retrieve (UUID, 32-character uppercase hexadecimal string)
    Example:
    24C9C2B19F1B46ED964CD6653FC10791
  • Mode of the study, accepts: test, active, or training.
    Example:
    active
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.
    Example:
    6153170BDE5244A0BB3DF169C4168483

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Successfully retrieved broadcast emails. status: success and errorData: null
Body ()
Root Schema : NotificationsDetailResponse
Type: object
Aggregated notification broadcast details combined with notification log metadata
Show Source
Nested Schema : NotificationsBroadcast
Type: object
Notification broadcast record representing a user-targeted notification with audit and delivery metadata
Show Source
Examples

400 Response

Error in request, check the request
Body ()
Root Schema : NotificationResponse
Type: object
Standard wrapper for API responses. Contains the request processing status, the result payload for successful requests, and error details when a request fails.
Show Source
  • ErrorResponseData
    Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
  • result
    Result payload for the request. The concrete type depends on the endpoint and is described in the corresponding API documentation.
  • Status of the request processing. SUCCESS indicates the request was processed without errors. Any other value indicates failure.
    Example: success
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
Result payload for the request. The concrete type depends on the endpoint and is described in the corresponding API documentation.
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
Examples

Back to Top