V1.0
post
/ec-notifications-svc/rest/v1.0/i18support/email/{templatetype}
Sends email to users with the specified template. Provide support to internationalization in addition to list of study role IDs and email addresses.
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 localized email based on template with subject structure, recipients, placeholder maps, and optional direct email addresses and study role IDs.
Show Source
-
emailAddresses: array
emailAddresses
Additional direct recipient email addresses
-
placeHolderImageMap: object
placeHolderImageMap
Placeholder images map used by the template, mapping keys to image URLs or identifiers
-
placeHolderValueMap: object
PlaceHolderValueMap
Container for placeholder properties used to build localized email content. Each property may define anchors for parameterized substitution.
-
studyRoleIds: array
studyRoleIds
List of study role identifiers to target
-
subject: object
Subject
Structured subject definition for i18n templates. Provides a message key and a collection of anchor values for substitution.
-
users: array
users
List of recipient user email addresses
Nested Schema : emailAddresses
Type:
arrayAdditional direct recipient email addresses
Show Source
-
Array of:
string
Additional direct recipient email addressesExample:
["user.surname@email.com"]
Example:
[
"user.surname@email.com"
]Nested Schema : placeHolderImageMap
Type:
objectPlaceholder images map used by the template, mapping keys to image URLs or identifiers
Example:
{
"logo":"https://cdn.example.com/assets/logo.png"
}Nested Schema : PlaceHolderValueMap
Type:
objectContainer for placeholder properties used to build localized email content. Each property may define anchors for parameterized substitution.
Show Source
-
properties: array
properties
List of placeholder properties to substitute within the template body.
Nested Schema : studyRoleIds
Type:
arrayList of study role identifiers to target
Show Source
-
Array of:
string
List of study role identifiers to targetExample:
["1BC29B36F5D64B1B95F4BD765EA481BE"]
Example:
[
"1BC29B36F5D64B1B95F4BD765EA481BE"
]Nested Schema : Subject
Type:
objectStructured subject definition for i18n templates. Provides a message key and a collection of anchor values for substitution.
Show Source
-
anchorKey: string
Message key used to resolve the localized email subject text.Example:
NTF_SIGN_OVERDUE -
anchorValues: object
AnchorValues
Container for key-value parameters that provide substitution values for a given anchor key.
Nested Schema : users
Type:
arrayList of recipient user email addresses
Show Source
-
Array of:
string
List of recipient user email addressesExample:
["C5770247BEF54CE0923B7C7CA3B659C8","DBF0480DD86446CE8482BE016726393C"]
Example:
[
"C5770247BEF54CE0923B7C7CA3B659C8",
"DBF0480DD86446CE8482BE016726393C"
]Nested Schema : properties
Type:
arrayList of placeholder properties to substitute within the template body.
Show Source
-
Array of:
object Properties
Represents a single placeholder property in the template body, optionally including anchors for parameterized substitution.
Nested Schema : Properties
Type:
objectRepresents a single placeholder property in the template body, optionally including anchors for parameterized substitution.
Show Source
-
anchors: array
anchors
Anchors used to substitute dynamic portions within the property value
-
propertyName: string
Name of the placeholder property in the template body. Some examples: NTF_DCS_ADV_EVENT, NTF_SIGN_OVERDUE, NTF_HEADER_C1, NTF_HEADER_SITE_NAME, NTF_HEADER_STUDY_MODE, NTF_HEADER_STUDY_NAME etcExample:
NTF_HEADER_SITE_NAME -
propertyValue: string
Value of the placeholder property prior to anchor substitution. Some examples: NTF_DCS_ADV_EVENT, NTF_SIGN_OVERDUE, NTF_HEADER_C1, NTF_HEADER_SITE_NAME, NTF_HEADER_STUDY_MODE, NTF_HEADER_STUDY_NAME etcExample:
NTF_HEADER_SITE_NAME
Nested Schema : anchors
Type:
arrayAnchors used to substitute dynamic portions within the property value
Show Source
-
Array of:
object Anchors
Anchor mapping used within template properties for text substitution. Associates an anchor key with its parameter values.
Nested Schema : Anchors
Type:
objectAnchor mapping used within template properties for text substitution. Associates an anchor key with its parameter values.
Show Source
-
anchorKey: string
Unique subject anchor key within the export payload. Some examples: NTF_ORS_DEPOT_LOW_KIT, NTF_ORS_BODY_STUDY_NAME, NTF_ORS_BODY_STUDY_ID, NTF_ORS_BODY_STUDY_MODE, NTF_ORS_MODE_ACTIVE, NTF_ORS_MODE_TEST, NTF_ORS_MODE_TRAINING, NTF_ORS_NEW_SHIPMENT_DEPOT_ID, NTF_ORS_NEW_SHIPMENT_DEPOT_NAME, NTF_ORS_DEPOT_ADDRESS, NTF_ORS_DATE_ALERT_RAISED, NTF_ORS_KIT_TYPE_ID, NTF_ORS_KIT_TYPE_DESCRIPTION, NTF_ORS_CURRENT_INVENTORY_AVAILABLE.Example:
NTF_SIGN_OVERDUE -
anchorValues: object
AnchorValues
Container for key-value parameters that provide substitution values for a given anchor key.
Nested Schema : AnchorValues
Type:
objectContainer for key-value parameters that provide substitution values for a given anchor key.
Show Source
-
keyValues: array
keyValues
List of key-value entries used to substitute placeholders for this anchor
Nested Schema : keyValues
Type:
arrayList of key-value entries used to substitute placeholders for this anchor
Show Source
-
Array of:
object KeyValues
Represents a single parameter for anchor substitution with an integer key, a value, and a type describing how to interpret the value.
Nested Schema : KeyValues
Type:
objectRepresents a single parameter for anchor substitution with an integer key, a value, and a type describing how to interpret the value.
Show Source
-
key: integer
(int32)
Integer key representing the position or identifier of the parameter in the anchor.Example:
0 -
type: string
Type of the value for rendering or validation. Typical values: TEXT, DATE.Example:
TEXT -
value: string
Parameter value to substitute.Example:
ACTIVE
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