REST API · Webhooks · Ticketing Handoff

FlowGuard does not need to replace your systems. It gives them better incident data.

FlowGuard captures the leak response as structured data — detection time, acknowledgement, responder actions, escalation path, photos, notes, containment, resolution, and reports. That record can be handed off through API, webhook, or ticketing workflows depending on what your existing systems support.

Book My Free Water-Risk WalkView Sample Report

We will not tell you every system is plug-and-play. Some platforms have clean APIs. Some need webhook handoff. Some need a lighter email/report workflow. We tell you which one you are actually getting before anything is installed.

The Payload

What FlowGuard can hand off.

Incident events

  • Leak detected
  • Alert sent
  • Acknowledged
  • En route
  • On site
  • Contained
  • Resolved

Responder activity

  • Who acknowledged
  • Who contained
  • Response timestamps
  • Ownership changes
  • Action notes

Evidence

  • Photos
  • Notes
  • Location / zone
  • Severity
  • Estimated loss prevented when applicable

Reports

  • Maintenance recap
  • Insurance-style documentation
  • Monthly summaries
  • Delivery logs

Status and closeout

  • False positive
  • Known issue
  • Resolved
  • Pending dry confirmation
  • Source / category when available

Methods

Three ways to integrate.

Method 01

REST API

For teams with internal tools or a system that can pull data, FlowGuard can expose structured incident records through scoped API endpoints. This is best when your team wants controlled access to incident history, reports, and response status.

Access is provisioned per implementation as a scoped path — not an open, public-by-default endpoint.

Method 02

Webhooks

For systems that can receive events, FlowGuard can send structured webhook payloads when incidents are created, acknowledged, contained, resolved, or closed out. This is the cleanest way to trigger downstream workflows without asking maintenance to enter the same event twice.

Delivery depends on the receiving system and the field mapping it expects.

Method 03

Ticketing / Work-Order Handoff

For ticketing or work-order systems, FlowGuard can hand off the incident summary, location, severity, responder actions, and report link. If the receiving system supports an API, we can map directly. If not, we use webhook, email, or report-based handoff.

The goal is not to pretend every platform works the same. The goal is to make sure the water incident does not die inside one dashboard.

The Honest Version

What we will not pretend.

We will not claim every PMS, CMMS, or work-order platform integrates the same way. They do not.

Some systems have modern APIs. Some have limited webhooks. Some only accept email-based intake. Some require custom mapping.

FlowGuard’s job is to capture the incident cleanly and hand it off in the safest format your stack can actually support.

  • We do not promise magic one-click integration.
  • We do not force your team to abandon existing systems.
  • We do not hide manual setup behind the word ‘seamless.’
  • We do not claim a ticket was created unless the receiving system confirms it.
  • We do not make your maintenance team enter the same incident twice if a cleaner handoff is available.

An Example

How a ticket handoff can work.

  1. 1Sensor detects water in Unit 204 Kitchen.
  2. 2FlowGuard opens the response path and alerts the right responder.
  3. 3Maintenance acknowledges, goes en route, arrives, contains, and resolves.
  4. 4FlowGuard creates a structured incident record.
  5. 5Depending on the system, FlowGuard can send a webhook event, create or update a ticket through API, send a structured email to the work-order inbox, or attach or link the incident report.
  6. 6The property keeps its normal system of record, but the water response gets documented correctly.

Technical Trust

Structured enough for software. Clear enough for operations.

Every incident becomes a clean, structured record your systems can consume — and your team can read. Exact fields vary by implementation and access level.

Event delivery
incident.detected
incident.acknowledged
incident.contained
incident.resolved
Webhook endpoint
REST API pull
Ticket / work order

Which path you get depends on the receiving system. We confirm it before anything is installed.

webhook payload
{
  "event": "incident.resolved",
  "property": "Sunset Apartments",
  "zone": "Unit 204 Kitchen",
  "severity": "standard",
  "detected_at": "...",
  "acknowledged_at": "...",
  "contained_at": "...",
  "resolved_at": "...",
  "responder": "Maintenance Lead",
  "photos_attached": true,
  "report_url": "..."
}

Access

Controlled access, not an open firehose.

Integrations should be scoped. FlowGuard should only send the data a downstream system needs: incident status, location, timestamps, responder actions, and report links. We do not treat integration as permission to spray sensitive property data everywhere.

  • Scoped API keys or approved endpoints
  • Event-specific webhooks
  • Property-level access boundaries
  • Delivery logs where supported
  • No unnecessary PII

Want to know what your systems can actually support?

Book a free water-risk walk. We’ll look at your property, your maintenance workflow, and the systems your team already uses — then tell you honestly whether API, webhook, ticket handoff, or report-based workflow makes the most sense.

Book My Free Water-Risk WalkView Sample Report