ITpipes API · Data and Workflow Gateway

Connect Your Sewer Inspection Data to Your System of Record

Condition data that reaches the people planning the work and defending the budget.

Your inspection program produces the most detailed record your utility has of what is happening underground. The ITpipes API puts that record into the systems where the decisions get made: the asset management system your crews work from, the warehouse your analysts query, and the model behind your capital plan.

The case for connecting

Six Things Your Program Stops Doing By Hand

Every one of these is work someone on your team is doing today with an export, a phone call, or a login they should not need.

Operations and Public Works

01 Know where the program stands without calling the field Match work between systems by work-order number or your own client reference, then check which inspections are finished. Crew productivity and program progress show up in the system your supervisors already have open, so a status update stops being a phone call.
02 Run the full work-order loop on whatever platform you use Raise inspection work in your own asset management system, have the crew complete it in ITpipes, pull the results back, and close it out. The same loop our Trimble, OpenGov, CentralSquare, and Novotx integrations run, now available to platforms we do not package a connector for.

Engineering and Condition Assessment

03 Pull the defects a study needs in one query Query by NASSCO code, severity grade, or location, across assets and inspections in a single call. A consulting engineer gets the defect data a rehabilitation or inflow and infiltration study needs without a login to your inspection software, and without waiting on your staff to assemble it.
04 Feed the models your decisions already rest on Condition data reaches your business intelligence, hydraulic modeling, and data science tools at full record-level detail. Risk scoring and rehabilitation ranking run on data as current as your last scheduled refresh instead of last year's extract.

Data, Reporting, and IT

05 Keep one current copy of the truth The version your analysts query and the version your crews recorded are the same version. Reporting stops depending on who pulled the last extract and when, and two departments stop arriving at a meeting with different numbers for the same network.
06 Stop buying a connector per system Operations runs work orders in an asset management system. Analysts build condition models in a warehouse. Engineers pull defects for a study. One interface serves all three, and it serves the next system on your network too.

Capital planning

The Detail That Carries a Capital Plan Through Budget Review

A rating tells you a pipe scored a 4. An observation tells you what is wrong with it, where along the run, and how bad. The ITpipes API returns the observations.

Level 1 Asset The physical thing. A mainline pipe, a manhole, or a lateral.
Level 2 Inspection One survey of that asset on one date, with its NASSCO ratings.
Level 3 Observation A single coded finding at a given distance. A crack, a root intrusion, a service connection. This is the level that sets rehabilitation priorities.

What every inspection carries

  • NASSCO pipe ratings calculated by ITpipes, so your team does not recompute them: OPR, SPR, and MPR, and up to six more
  • Which ratings you receive depends on what your inspection template defines, which is set by what matters to your team
  • Video and images on the paged inspection list, each with a file name and a media URL

What every observation carries

  • Its NASSCO code
  • Its severity grade
  • Its distance along the asset

At budget time that detail does the arguing for you. A rehabilitation list built on defect level records, carried straight from the inspection system into the report your council sees, answers why this pipe and why this year without anyone rebuilding the case by hand.

It compounds over time. Every inspection your crews run adds to a record that your condition models, your risk scoring, and your rehabilitation ranking can read directly from CoreVision. The value of the program you have already paid for goes up each year the data stays connected, rather than aging inside an export somebody made once.

The API returns the underlying records at full detail, and your systems decide what to do with them. No summary layer sits in between deciding what you get to see.

Access control

Give Visibility.
Keep Control.

The split is deliberate, and it is what makes the rest of this page safe to act on. A utility can give read access to a consultant, a dashboard, or a business intelligence tool without giving anyone the ability to change what the crew recorded. The record of your network stays the record of your network.

Read key

Goes to whoever needs the data

Assets, inspections, observations, defect filters, completion checks. Read-only: it cannot create or change anything in ITpipes.

Write key

Stays with your team

Creating assets and inspections, and setting the work-order fields. Issued separately, for the systems that drive the work-order loop.

Questions

Frequently Asked Questions

What is the ITpipes API?
The ITpipes API is a data and workflow solution that gives your own systems direct, programmatic access to the inspection data in your ITpipes platform: the assets, the inspections performed against them, and the NASSCO-coded observations recorded during those inspections. It also lets your work-order system create inspections in ITpipes and close them out, without ITpipes building a custom integration for your platform.
Do we need the API if we already have a packaged ITpipes connector?
If you run Trimble, OpenGov, CentralSquare, Novotx, or any other AMS supported by a current integration, those integrations are the fastest path for work order and inspection sync. Adding the ITpipes API allows for observation level data to flow into those systems, assuming there is a place within the AMS for this information to be stored.
What data does the ITpipes API return?
Assets, inspections, and observations, at full record-level detail, for mainline pipes, manholes, and laterals. Assets carry their identifying and location detail, inspections carry their date and NASSCO ratings, and observations carry the NASSCO code, severity grade, and distance for each coded finding.
Does the ITpipes API include NASSCO condition ratings?
Yes. ITpipes calculates OPR, SPR, and MPR and returns them on every inspection, so your team does not have to compute them.
Can our system create inspections and close out work orders?
Yes, with a write key. Your system can create open work, including the asset and an open inspection record, in ITpipes. It can set the work-order status fields, which is what lets a full work-order loop run between your asset management system and ITpipes.
Can we get inspection video and images through the API?
Yes. Video and images come back with the paged inspection list, each with a file name and a download link. Download links are generated fresh and are short-lived by design, so your system should store the file name and request a new link at the moment it actually needs the file, rather than saving links into a warehouse column.

Ready to Open the Gateway

We turn on access and issue the keys, and your team sets up the data flow into the systems you already use.