Determine if given recipients are valid
post
/20241001/actions/validateRecipients
Verifies that the given personnel inboxes, group inboxes, or both are valid recipients and can receive the provided category of messages in their inbox.
This is not a search API. It is an explicit check on provided IDs.
Request
Header Parameters
-
accept: string
Specifies which media types are acceptable for the response. Defaults to
application/json.Default Value:application/json -
accept-charset: string
Specifies which character sets are acceptable for the response. Defaults to
UTF-8.Default Value:UTF-8 -
authorization(required): string
Contains the credentials to authenticate a consumer to the service.
-
opc-request-id: string
Unique Oracle Health assigned identifier for the request. If you need to contact Oracle about a particular request, provide the request ID. The only valid characters for request IDs are letters, numbers, underscore, and dash.
Details about the recipients to be validated.
Root Schema : ValidateRecipientsDetails
Type:
objectThe request object containing the list of recipients to validate and additional validation criteria.
Show Source
-
category(required):
string
Allowed Values:
[ "MESSAGES", "REMINDERS" ]The type of message. Validates that the recipients are configured to recieve this message category. -
patientId:
string
The identifier of a patient. Currently validates that the recipients share a logical domain with the patient. Eventually it will be used to mark recipients as valid if they have access to the patient's chart.Example:
2222 -
recipients(required):
array recipients
The list of recipients to be validated. Can contain either personnel, group inboxes, or a mix of both.
Nested Schema : recipients
Type:
arrayThe list of recipients to be validated. Can contain either personnel, group inboxes, or a mix of both.
Show Source
-
Array of:
object Recipient
Recipient details
Nested Schema : Recipient
Type:
objectRecipient details
Show Source
-
id(required):
string
The identifier of the recipient.Example:
1111 -
recipientType(required):
string
Allowed Values:
[ "GROUPINBOX", "PERSONNEL" ]The type of recipient.
Response
Supported Media Types
- application/json
200 Response
Recipients validated successfully
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ValidatedRecipientCollection
Type:
objectThe results of validating the recipients
Show Source
-
items(required):
array items
The list of validated recipient details. Each requested recipient is returned, but order is not guaranteed.
Nested Schema : items
Type:
arrayThe list of validated recipient details. Each requested recipient is returned, but order is not guaranteed.
Show Source
-
Array of:
object ValidatedRecipientSummary
The information about a validated recipient.
Nested Schema : ValidatedRecipientSummary
Type:
objectThe information about a validated recipient.
Show Source
-
id(required):
string
The identifier of the recipient.Example:
1111 -
isValid(required):
boolean
Trueindicates the recipient is valid and able to receive notifications. -
recipientType(required):
string
Allowed Values:
[ "GROUPINBOX", "PERSONNEL" ]The type of recipient.
400 Response
Bad Request
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
401 Response
Unauthorized
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
404 Response
Not Found
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
422 Response
Unprocessable Entity
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
429 Response
Too Many Requests
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
500 Response
Internal Server Error
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.