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
  • 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, AssignedTrainingTemplate
    Example:
    DefaultTrainingTemplate
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Request 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
Nested Schema : emailAddresses
Type: array
Additional direct recipient email addresses
Show Source
  • Additional direct recipient email addresses
    Example: ["user.surname@email.com"]
Example:
[
    "user.surname@email.com"
]
Nested Schema : placeHolderImageMap
Type: object
Placeholder 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: object
Container for placeholder properties used to build localized email content. Each property may define anchors for parameterized substitution.
Show Source
Nested Schema : studyRoleIds
Type: array
List of study role identifiers to target
Show Source
  • List of study role identifiers to target
    Example: ["1BC29B36F5D64B1B95F4BD765EA481BE"]
Example:
[
    "1BC29B36F5D64B1B95F4BD765EA481BE"
]
Nested Schema : Subject
Type: object
Structured subject definition for i18n templates. Provides a message key and a collection of anchor values for substitution.
Show Source
Nested Schema : users
Type: array
List of recipient user email addresses
Show Source
  • List of recipient user email addresses
    Example: ["C5770247BEF54CE0923B7C7CA3B659C8","DBF0480DD86446CE8482BE016726393C"]
Example:
[
    "C5770247BEF54CE0923B7C7CA3B659C8",
    "DBF0480DD86446CE8482BE016726393C"
]
Nested Schema : properties
Type: array
List of placeholder properties to substitute within the template body.
Show Source
  • Properties
    Represents a single placeholder property in the template body, optionally including anchors for parameterized substitution.
Nested Schema : Properties
Type: object
Represents a single placeholder property in the template body, optionally including anchors for parameterized substitution.
Show Source
  • anchors
    Anchors used to substitute dynamic portions within the property value
  • 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 etc
    Example: NTF_HEADER_SITE_NAME
  • 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 etc
    Example: NTF_HEADER_SITE_NAME
Nested Schema : anchors
Type: array
Anchors used to substitute dynamic portions within the property value
Show Source
  • Anchors
    Anchor mapping used within template properties for text substitution. Associates an anchor key with its parameter values.
Nested Schema : Anchors
Type: object
Anchor mapping used within template properties for text substitution. Associates an anchor key with its parameter values.
Show Source
  • 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
    Container for key-value parameters that provide substitution values for a given anchor key.
Nested Schema : AnchorValues
Type: object
Container for key-value parameters that provide substitution values for a given anchor key.
Show Source
Nested Schema : keyValues
Type: array
List of key-value entries used to substitute placeholders for this anchor
Show Source
  • 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: object
Represents a single parameter for anchor substitution with an integer key, a value, and a type describing how to interpret the value.
Show Source
  • Integer key representing the position or identifier of the parameter in the anchor.
    Example: 0
  • Type of the value for rendering or validation. Typical values: TEXT, DATE.
    Example: TEXT
  • Parameter value to substitute.
    Example: ACTIVE
Examples

Back to Top

Response

Supported Media Types

202 Response

Request processed successfully, check the result

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