Hold Request Creation Response in the JSON Format
The following code snippet illustrates how the attribute/value pairs are structured while sending the hold request creation response in the JSON format:
{
"C1-CreateHoldRequest":
{
"holdRequest": ""
{
"statusCd": ""
"holdRequestId": ""
"holdStatus": ""
"messageText": ""
"sourceSystem": ""
"externalTransactionId": ""
"externalSourceId": ""
"holdStartDate": ""
"holdEndDate": ""
"holdDays": ""
"holdRequestType": ""
"holdEntity": ""
"holdReason": ""
"holdComments": ""
"entityIdentifierType": ""
"entityIdentifierValue": ""
"entityId": ""
"holdEntityEndDate": ""
"hierarchySwitch": ""
"holdProcessData":
{
"holdProcess": ""
"holdProcessEndDate": ""
}
characteristics":
{
"characteristicType": ""
"characteristicValue": ""
"effectiveDate": ""
}
}
}
}Related Topics
| For more information on... | See... |
|---|---|
| Hold Request Creation Request in the JSON Format | Hold Request Creation Request in the JSON Format |
| Hold Request Creation Request and Response - Attribute/Value Pairs in JSON Format | Hold Request Creation Request and Response - Attribute/Value Pairs in JSON Format |
| Sample Hold Request Creation Request and Response in the JSON Format | Sample Hold Request Creation Request and Response in the JSON Format |