V5.0
post
/ec-notifications-svc/rest/v5.0/studies/{studyId}/{mode}/notificationlog
Creates a log entry and immediately broadcast it or schedules it. This version supports anchor index which enables having multiple values for an anchor key. Relative to v4.0: adds anchorIndex on body anchors to disambiguate repeated keys.
Request
Path Parameters
-
mode(required): string
Mode of the study, accepts: test, active, or training.Example:
active -
studyId(required): string
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.Example:
62A16307A4F4479D9415FE7DB0EA0233
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
object-
approvalFlag(required): string
Minimum Length:
0Maximum Length:1Allowed Values:[ "Y", "N" ]Approval flag indicating if approval is requiredExample:Y -
attachment: string
Attachment content as base64 encoded bytesExample:
SGVsbG8gd29ybGQh11 -
attachmentProviderVersion: string
Provider API version used to generate the attachment URLExample:
null -
attachmentUrl: string
Attachment URL reference when content is not embeddedExample:
null -
attachmentUrlProvider: string
Provider of the attachment URLExample:
null -
category(required): string
Functional category of the notification. Some examples: Shipment Failure, Site state Change, Report Generation etc.Example:
Report Generation -
comment: string
Minimum Length:
0Maximum Length:2048CommentExample:Shipment Failure Notification -
createdBy(required): string
User or process that created the notificationExample:
Eva, Hulshagen -
createdDate: string
(date-time)
Creation timestamp of the notificationExample:
2025-03-21T10:20:30Z -
emailAddressList: string
Minimum Length:
0Maximum Length:4000Comma separated list of email addressesExample:john.doe@oracle.com,jane.doe@oracle.com -
emailOnlyFlag: string
Minimum Length:
0Maximum Length:1Allowed Values:[ "y", "n" ]Send only email without in-app notificationExample:n -
entityId: string
Unique identifier (UUID, 32-character uppercase hexadecimal string) of the entity for which the property applies.Example:
1BC29B36F5D64B1B95F4BDBBCEA481BE -
entityType(required): string
Entity type associated with the notification. Some examples: Study, Site, Subject.Example:
Site -
id: string
Unique identifier of the notification log record (UUID, 32-character uppercase hexadecimal string)Example:
33D0D74837F6454B836AAB5BA2574D28 -
immediateFlag(required): string
Minimum Length:
0Maximum Length:1Allowed Values:[ "y", "n" ]Immediate processing flagExample:n -
messageDescription: string
Minimum Length:
0Maximum Length:32767Detailed message body of the notificationExample:Drug Order ID:09009Original Request Date: Eastern Time (US & Cananda): 21-May-2012 9:45 PManual Request Date: Eastern Time (US & Canada): 19-Jul-2016 3:56 PSite ID: 50Site Name: UAT, Claudia DabijaSite Address: 12 West RD, Phoenix, ARequestor Name: Eva, HulshageEmail: eva.hulshagen@oracle.coPlease complete the Manual request here. If you do not have the access to the drg supply system, please contact the Sponsor to verify you have received the cancel request and the drugs listed in this shipment have not left the possession of the depot. -
messageLanguageSupported: object
MessageLanguageSupportedDto2
Structure holding localized message subject and body with indexed anchors for deterministic replacement order
-
messageSubject: string
Minimum Length:
0Maximum Length:1024Subject/title of the notificationExample:Cancellation Shipment Request -
notificationDateTime: string
Time when the notification was sent or scheduledExample:
2025-03-21T10:20:30.000Z -
ObjectVersionNumber: number
Object version number used for concurrency control.Example:
1 -
operationType: string
Operation type on the record, can have values CREATED, MODIFIED or REMOVEDExample:
CREATED -
priority(required): string
Allowed Values:
[ "LOW", "HIGH", "0", "1" ]Priority of the notificationExample:HIGH -
privilege: string
Business right or privilege associated with this notification. Some examples: SiteStatusChangeNotification, ReportNotificationExample:
SiteStatusChangeNotification -
reason: string
Minimum Length:
0Maximum Length:255ReasonExample:Inventory control system failure -
serviceName(required): string
Allowed Values:
[ "dc", "ors", "reporting", "ruledesigner", "sites" ]Service name that generated the notificationExample:dc -
SoftwareVersionNumber: number
Software version number used when the record was generated.Example:
1 -
targetList: array
targetList
List on ORS site information
-
userId: string
Unique Identifier (UUID, 32-character uppercase hexadecimal string) of the userExample:
D79F8A8A1B9E4F9A9A25E3B3B1C2D3E4 -
userList: string
Minimum Length:
0Maximum Length:4000Comma separated list of user identifiers targeted by this notificationExample:1BC29B36F5D64B1B95F4B987CEA481BE,1BC29B36F5D64B1B95F4BD234EA481BE -
versionEnd: string
The end date until which the data is applicable or valid.Example:
2025-03-21T10:20:30.000Z -
versionStart: string
The timestamp marking the beginning of the validity period for this record version within the system.Example:
2025-03-20T10:20:30.000Z
Nested Schema : MessageLanguageSupportedDto2
Type:
objectStructure holding localized message subject and body with indexed anchors for deterministic replacement order
Show Source
-
body(required): object
BodyDto2
Notification body template for v5 including HTML content and indexed anchors for deterministic replacement
-
subject(required): object
SubjectDto
Subject anchor and associated value entries
Nested Schema : targetList
Type:
arrayList on ORS site information
Show Source
-
Array of:
object NotificationLogTargetDto
Target mapping linking a notification to an entity such as a site or depot
Nested Schema : BodyDto2
Type:
objectNotification body template for v5 including HTML content and indexed anchors for deterministic replacement
Show Source
-
anchors(required): array
anchors
List of body anchors with index and their substitution values
-
htmlContent: string
HTML content template for the notification bodyExample:
Study updated
Nested Schema : SubjectDto
Type:
objectSubject anchor and associated value entries
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_ORS_DEPOT_LOW_KIT -
values: array
values
Collection of key-type-name entries for this subject
Example:
{
"anchorKey":"NTF_ORS_DEPOT_LOW_KIT",
"values":[
{
"key":"101",
"keyType":"VISIT",
"name":"Visit 1"
}
]
}Nested Schema : anchors
Type:
arrayList of body anchors with index and their substitution values
Show Source
-
Array of:
object NotificationAnchorDto2
Anchor replacement entry for localized message body with indexed anchors.
Nested Schema : NotificationAnchorDto2
Type:
objectAnchor replacement entry for localized message body with indexed anchors.
Show Source
-
anchorIndex(required): integer
0-based index of the anchor occurrence within the message body.Example:
0 -
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_ORS_BODY_STUDY_NAME -
values: array
values
List of substitution values for this anchor
Nested Schema : values
Type:
arrayList of substitution values for this anchor
Show Source
-
Array of:
object ValueDto
Key, type, and display name entry for a subject
Nested Schema : ValueDto
Type:
objectKey, type, and display name entry for a subject
Show Source
-
key: string
Numeric key associated with the entryExample:
1 -
keyType(required): string
Type/category for the keyExample:
TEXT or DATE -
name: string
Human-readable label for the entryExample:
Visit 1
Nested Schema : values
Type:
arrayCollection of key-type-name entries for this subject
Show Source
-
Array of:
object ValueDto
Key, type, and display name entry for a subject
Nested Schema : NotificationLogTargetDto
Type:
objectTarget mapping linking a notification to an entity such as a site or depot
Show Source
-
targetId(required): string
Unique identifier(UUID, 32-character uppercase hexadecimal string) for the coding result target.Example:
515D8531E6A94B1BB238E58A572D8C80 -
targetType(required): string
Type of notification target. Some examples: SITE, DEPOT USERExample:
SITE
Examples
Back to Top
Response
Supported Media Types
- application/json
202 Response
Request processed successfully, check the result
Root Schema : schema
Type:
Show Source
object-
approvalFlag(required): string
Minimum Length:
0Maximum Length:1Allowed Values:[ "Y", "N" ]Approval flag indicating if approval is requiredExample:Y -
attachment: string
Attachment content as base64 encoded bytesExample:
SGVsbG8gd29ybGQh11 -
attachmentProviderVersion: string
Provider API version used to generate the attachment URLExample:
null -
attachmentUrl: string
Attachment URL reference when content is not embeddedExample:
null -
attachmentUrlProvider: string
Provider of the attachment URLExample:
null -
category(required): string
Functional category of the notification. Some examples: Shipment Failure, Site state Change, Report Generation etc.Example:
Report Generation -
comment: string
Minimum Length:
0Maximum Length:2048CommentExample:Shipment Failure Notification -
createdBy(required): string
User or process that created the notificationExample:
Eva, Hulshagen -
createdDate: string
(date-time)
Creation timestamp of the notificationExample:
2025-03-21T10:20:30Z -
emailAddressList: string
Minimum Length:
0Maximum Length:4000Comma separated list of email addressesExample:john.doe@oracle.com,jane.doe@oracle.com -
emailOnlyFlag: string
Minimum Length:
0Maximum Length:1Allowed Values:[ "y", "n" ]Send only email without in-app notificationExample:n -
entityId: string
Unique identifier (UUID, 32-character uppercase hexadecimal string) of the entity for which the property applies.Example:
1BC29B36F5D64B1B95F4BDBBCEA481BE -
entityType(required): string
Entity type associated with the notification. Some examples: Study, Site, Subject.Example:
Site -
id: string
Unique identifier of the notification log record (UUID, 32-character uppercase hexadecimal string)Example:
33D0D74837F6454B836AAB5BA2574D28 -
immediateFlag(required): string
Minimum Length:
0Maximum Length:1Allowed Values:[ "y", "n" ]Immediate processing flagExample:n -
messageDescription: string
Minimum Length:
0Maximum Length:32767Detailed message body of the notificationExample:Drug Order ID:09009Original Request Date: Eastern Time (US & Cananda): 21-May-2012 9:45 PManual Request Date: Eastern Time (US & Canada): 19-Jul-2016 3:56 PSite ID: 50Site Name: UAT, Claudia DabijaSite Address: 12 West RD, Phoenix, ARequestor Name: Eva, HulshageEmail: eva.hulshagen@oracle.coPlease complete the Manual request here. If you do not have the access to the drg supply system, please contact the Sponsor to verify you have received the cancel request and the drugs listed in this shipment have not left the possession of the depot. -
messageLanguageSupported: object
MessageLanguageSupportedDto2
Structure holding localized message subject and body with indexed anchors for deterministic replacement order
-
messageSubject: string
Minimum Length:
0Maximum Length:1024Subject/title of the notificationExample:Cancellation Shipment Request -
notificationDateTime: string
Time when the notification was sent or scheduledExample:
2025-03-21T10:20:30.000Z -
ObjectVersionNumber: number
Object version number used for concurrency control.Example:
1 -
operationType: string
Operation type on the record, can have values CREATED, MODIFIED or REMOVEDExample:
CREATED -
priority(required): string
Allowed Values:
[ "LOW", "HIGH", "0", "1" ]Priority of the notificationExample:HIGH -
privilege: string
Business right or privilege associated with this notification. Some examples: SiteStatusChangeNotification, ReportNotificationExample:
SiteStatusChangeNotification -
reason: string
Minimum Length:
0Maximum Length:255ReasonExample:Inventory control system failure -
serviceName(required): string
Allowed Values:
[ "dc", "ors", "reporting", "ruledesigner", "sites" ]Service name that generated the notificationExample:dc -
SoftwareVersionNumber: number
Software version number used when the record was generated.Example:
1 -
targetList: array
targetList
List on ORS site information
-
userId: string
Unique Identifier (UUID, 32-character uppercase hexadecimal string) of the userExample:
D79F8A8A1B9E4F9A9A25E3B3B1C2D3E4 -
userList: string
Minimum Length:
0Maximum Length:4000Comma separated list of user identifiers targeted by this notificationExample:1BC29B36F5D64B1B95F4B987CEA481BE,1BC29B36F5D64B1B95F4BD234EA481BE -
versionEnd: string
The end date until which the data is applicable or valid.Example:
2025-03-21T10:20:30.000Z -
versionStart: string
The timestamp marking the beginning of the validity period for this record version within the system.Example:
2025-03-20T10:20:30.000Z
Nested Schema : MessageLanguageSupportedDto2
Type:
objectStructure holding localized message subject and body with indexed anchors for deterministic replacement order
Show Source
-
body(required): object
BodyDto2
Notification body template for v5 including HTML content and indexed anchors for deterministic replacement
-
subject(required): object
SubjectDto
Subject anchor and associated value entries
Nested Schema : targetList
Type:
arrayList on ORS site information
Show Source
-
Array of:
object NotificationLogTargetDto
Target mapping linking a notification to an entity such as a site or depot
Nested Schema : BodyDto2
Type:
objectNotification body template for v5 including HTML content and indexed anchors for deterministic replacement
Show Source
-
anchors(required): array
anchors
List of body anchors with index and their substitution values
-
htmlContent: string
HTML content template for the notification bodyExample:
Study updated
Nested Schema : SubjectDto
Type:
objectSubject anchor and associated value entries
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_ORS_DEPOT_LOW_KIT -
values: array
values
Collection of key-type-name entries for this subject
Example:
{
"anchorKey":"NTF_ORS_DEPOT_LOW_KIT",
"values":[
{
"key":"101",
"keyType":"VISIT",
"name":"Visit 1"
}
]
}Nested Schema : anchors
Type:
arrayList of body anchors with index and their substitution values
Show Source
-
Array of:
object NotificationAnchorDto2
Anchor replacement entry for localized message body with indexed anchors.
Nested Schema : NotificationAnchorDto2
Type:
objectAnchor replacement entry for localized message body with indexed anchors.
Show Source
-
anchorIndex(required): integer
0-based index of the anchor occurrence within the message body.Example:
0 -
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_ORS_BODY_STUDY_NAME -
values: array
values
List of substitution values for this anchor
Nested Schema : values
Type:
arrayList of substitution values for this anchor
Show Source
-
Array of:
object ValueDto
Key, type, and display name entry for a subject
Nested Schema : ValueDto
Type:
objectKey, type, and display name entry for a subject
Show Source
-
key: string
Numeric key associated with the entryExample:
1 -
keyType(required): string
Type/category for the keyExample:
TEXT or DATE -
name: string
Human-readable label for the entryExample:
Visit 1
Nested Schema : values
Type:
arrayCollection of key-type-name entries for this subject
Show Source
-
Array of:
object ValueDto
Key, type, and display name entry for a subject
Nested Schema : NotificationLogTargetDto
Type:
objectTarget mapping linking a notification to an entity such as a site or depot
Show Source
-
targetId(required): string
Unique identifier(UUID, 32-character uppercase hexadecimal string) for the coding result target.Example:
515D8531E6A94B1BB238E58A572D8C80 -
targetType(required): string
Type of notification target. Some examples: SITE, DEPOT USERExample:
SITE
Examples
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