[Deprecated]: V2.0
post
/ec-notifications-svc/rest/v2.0/email/{templatetype}
Deprecated: Sends email to users with the specified template. Supports a list of email addresses. Relative to v1.0: Support email addresses of user to send notifications.
Request
Path Parameters
-
templatetype(required): string
Name of the template to use to send email. Valid values are taken from email template configuration database, Allowed Values: CompletedTrainingTemplate, DefaultTrainingTemplate_L10n, CompletedTrainingTemplate_L10n, WithoutStudyTrainingTemplate, AssignedTrainingTemplateExample:
DefaultTrainingTemplate
Supported Media Types
- application/json
Root Schema : schema
Type:
objectRequest body for sending an email based on a predefined template by allowing direct recipient email addresses in addition to users and placeholder maps.
Show Source
-
emailAddresses: array
emailAddresses
Additional recipient email addresses not associated with users
-
placeHolderImageMap: object
placeHolderImageMap
Map of placeholder image variables to URLs or resource identifiers
-
placeHolderValueMap: object
placeHolderValueMap
Map of placeholder variables to be replaced in the template body
-
subject(required): string
Email subject line to use when sending the templateExample:
Training Status Reminder -
users: array
users
List of recipient user identifiers (UUID, 32-character uppercase hexadecimal string)
Nested Schema : emailAddresses
Type:
arrayAdditional recipient email addresses not associated with users
Show Source
-
Array of:
string
Additional recipient email addresses not associated with usersExample:
["john.doe@oracle.com"
Example:
["john.doe@oracle.com"Nested Schema : placeHolderImageMap
Type:
objectMap of placeholder image variables to URLs or resource identifiers
Example:
{
"image5":"NOTIFICATION.EMAIL.IMAGE5",
"image3":"NOTIFICATION.EMAIL.IMAGE3",
"image4":"NOTIFICATION.EMAIL.IMAGE4",
"image1":"NOTIFICATION.EMAIL.IMAGE1",
"image2":"NOTIFICATION.EMAIL.IMAGE2"
}Nested Schema : placeHolderValueMap
Type:
objectMap of placeholder variables to be replaced in the template body
Example:
{
"userTrainingDetails":" ",
"redirectUrl":"",
"username":"system",
"studyName":"AutomationStudy"
}Nested Schema : users
Type:
arrayList of recipient user identifiers (UUID, 32-character uppercase hexadecimal string)
Show Source
-
Array of:
string
List of recipient user identifiers (UUID, 32-character uppercase hexadecimal string)Example:
["C5770247BEF54CE0923B7C7CA3B659C8","DBF0480DD86446CE8482BE016726393C"]
Example:
[
"C5770247BEF54CE0923B7C7CA3B659C8",
"DBF0480DD86446CE8482BE016726393C"
]Examples
Back to Top
Response
Supported Media Types
- application/json
202 Response
Request processed successfully, check the result
400 Response
Error in request, check the request
Root Schema : NotificationResponse
Type:
objectStandard wrapper for API responses. Contains the request processing status, the result payload for successful requests, and error details when a request fails.
Show Source
-
errorData: object
ErrorResponseData
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
-
result: object
result
Result payload for the request. The concrete type depends on the endpoint and is described in the corresponding API documentation.
-
status: string
Status of the request processing. SUCCESS indicates the request was processed without errors. Any other value indicates failure.Example:
success
Nested Schema : ErrorResponseData
Type:
objectStructure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
-
details: object
details
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
-
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
Nested Schema : result
Type:
objectResult payload for the request. The concrete type depends on the endpoint and is described in the corresponding API documentation.
Nested Schema : details
Type:
objectDetailed 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: userIdExamples