Skip to main content

Write Operation Failure

Write Operation Failure Webhook​

The WRITE_OPERATION_FAILURE webhook is sent when an integration fails to write data to the connected property management system. This event alerts you that a write operation was unable to complete successfully, which may require investigation or remediation.

When It Triggers​

A WRITE_OPERATION_FAILURE webhook is triggered in situations such as:

  • An API outage or downtime in the connected property management system.
  • Authentication or authorization failures preventing data writes.
  • Data write requests timing out.
  • Validation errors or data conflicts in the target system.

Common Use Cases​

  • Alerting internal teams so they can quickly investigate and resolve the issue.
  • Logging failures for audit purposes, SLA tracking, or error reporting dashboards.

Example Payload​

Example payload
{
  "trigger": "WRITE_OPERATION_FAILURE",
  "data": {
    "event": "WRITE_OPERATION_FAILURE",
    "integration_id": "INTEGRATION_ID_002",
    "vendor": "RESMAN",
    "root_job_id": "ROOT_OPERATION_ID_002",
    "write_status": "PARTIAL_SUCCESS",
    "errors": [
      "Failed to write resident transaction: Duplicate transaction ID"
    ]
  }
}

Field Reference​

  • trigger – The webhook trigger type.
  • data – The payload data object containing event details.
    • event – The webhook event type.
    • integration_id – Unique ID for the integration.
    • vendor – The PMS vendor for the integration.
    • root_job_id – The root job that initiated the process.
    • write_status – The status of the write operation (e.g., PARTIAL_SUCCESS, FAILURE).
    • errors – Array of error messages describing what went wrong.