Sample Hold Request Release Request and Response in the JSON Format
Using the below example, you can release a hold request with an Active status for the 44776611339988 hold request ID.
Sample Hold Request View Request in the JSON Format
{
"C1-ReleaseHoldRequest":
{
"sourceSystem": "SRC_PANAMER_PRIME"
"externalTransactionId": "ETI01"
"externalSourceId": "ESI05"
"holdRequestId": "44776611339988"
"holdReleaseReason": "FLOODS"
"holdComments": "HEAVY FLOODS IN DOWNTOWN"
}
}
Sample Hold Request Release Response in the JSON Format
{
"C1-ReleaseHoldRequest":
{
"requestProcessStatus": "SUCCESS"
"sourceSystem": "SRC_PANAMER_PRIME"
"externalTransactionId": "ETI01"
"externalSourceId": "ESI05"
"holdRequestId": "44776611339988"
"holdReleaseReason": "FLOODS"
"holdComments": "HEAVY FLOODS IN DOWNTOWN"
"holdEndDate": "2022-02-28"
"holdRequestStatus": "RELEASE"
"errormsg": ""
}
}
The following information is received from the hold request when the hold request ID passed in the release request is invalid.
{
"C1-ReleaseHoldRequest":
{
"requestProcessStatus": "FAILURE"
"sourceSystem": "SRC_PANAMER_PRIME"
"externalTransactionId": "ETI01"
"externalSourceId": "ESI05"
"holdRequestId": "55772211339988"
"holdReleaseReason": "FLOODS"
"holdComments": "HEAVY FLOODS IN DOWNTOWN"
"holdEndDate": ""
"holdRequestStatus": ""
"errormsg": "The hold request ID 55772211339988 is invalid"
}
}
Note: We have given the above request and response samples to illustrate
how the attribute value pairs should be structured while sending a
hold release request from the external system. However, you should
not seamlessly use this request sample in your environment because
the required pre-requisite data may not be available in your environment.
In such case, the system will give erroneous results.
Related Topics
For more information on... | See... |
---|---|
Hold Request Release Request and Response - Attribute/Value Pairs in JSON Format | Hold Request Release Request and Response - Tags in JSON Format |