Track Receiver

This documentation will describe the Track Receiver (XMHSTOPT) endpoint. This endpoint allows users to view the receiver responsible for the specified alarm event.

See the Authentication documentation for information on how to obtain the authentication headers within the request.

Use cases

  • View the receiver a signal originated from.

Supported attributes

AttributeTypeRequiredDescription
*setMethodstringYesDetermines the endpoint you are calling. Must be XMHSTOPT to view the receiver.
OPTIONstringYesDetermines the method you will be using. Use TRACK_REC to view the receiver.
INCIDENT_NUMBERstringYesThe unique identifier created by the system and assigned to the event. See the View Account History endpoint documentation for instructions on how to obtain event incident numbers.

Example request

curl --location "https://example.securemcloud.com/rest/rest.php?dataSource=methods&*view=xmsubmit" \
--header 'X-DICE-APPKEY: {{X-DICE-APPKEY}}' \
--header 'X-DICE-USERNAME: {{X-DICE-USERNAME}}' \
--header 'X-DICE-DATE: {{X-DICE-DATE}}' \
--header 'X-DICE-NONCE: {{X-DICE-NONCE}}' \
--header 'X-DICE-DIGEST: {{X-DICE-DIGEST}}' \
--header 'Accept: application/json' \
--form '*setMethod="XMHSTOPT"' \
--form 'OPTION="TRACK_REC"' \
--form 'INCIDENT_NUMBER="736663,n"'

Example response

{
    "RECEIVER_MSG": "Signal came from SURGARD #1 DV."
}

Possible error messages

Invalid method

Verify XMHSTOPT is specified for the *setMethod attribute.

{
    "ERROR_CODE": "999",
    "ERROR_DESCRIPTION": "INVALID%20METHOD%20METHOD",
    "PROGRAM_ERROR": "11",
    "PROGRAM_ERROR_DESCRIPTION": "Missing%20or%20Duplicate%20key",
    "ERROR_ON_LINE": "240",
    "ADDITIONAL_INFO": "%3CMETHOD_NAME%3EXMHSTOP%20%3C%2FMETHOD_NAME%3E"
}

Malformed XML

Verify you are specifying TRAC_REC as the option.

{
    "status": "error",
    "message": "XML is malformed",
    "errno": 2,
    "errstr": "simplexml_load_string(): Entity: line 2: parser error : Start tag expected, '<' not found"
}

Unable to find receiver

Verify the specified incident number is properly formatted and valid.

{
    "RECEIVER_MSG": "Unable to find receiver."
}