Retrieves the status of the contact restrict operation.
| Name | Type | | Description |
|---|
| operationID | GUID | Required | ID of the operation you are checking the status of. |
| Status | Name | Type | Description |
|---|
| 200 | | | Restrict request response |
| | operationInitiated | boolean | System-initiated restrict operation. |
| | operationID | integer | Auto-generated restrict operation ID. Keep track of this ID because it allows you to check the status of a restriction and decide how to proceed if there is a failure. |
| | requestServiceMessageID | guid | Service message ID for the request. |
| | responseDateTime | integer | The datetime restrict response is created in the system in GMT time. |
| | hasErrors | boolean | The requested operation is initiated with an error or not. |
| | resultMessages | array | Array of messages about the restrict operation. |
| | serviceMessageID | guid | Service message ID for the response. |
| | | | |
| 400 | | | Bad restrict request response |
| | operationInitiated | boolean | System-initiated restrict operation. |
| | operationID | integer | Auto-generated restrict operation ID. Keep track of this ID because it allows you to check the status of a restriction and decide how to proceed if there is a failure. |
| | requestServiceMessageID | guid | Service message ID for the request. |
| | responseDateTime | integer | The datetime restrict response is created in the system in GMT time. |
| | hasErrors | boolean | The requested operation is initiated with error or not. For a 400 response this is true. |
| | resultMessages | array | Array of messages about the restrict operation, with details about the bad request, like resulttype and resultcode. |
| | serviceMessageID | guid | Service message ID for the response. |