Pipeline Status Monitoring

Overview

The Pipeline Status API helps you monitor the health and freshness of your Kroo data pipelines. Use it to:

Track data freshness - See when each pipeline last synced data
Determine data availability - View scheduled next sync times for planning
Identify sync issues - Spot pipelines that haven’t updated recently
Create dashboards - Build PowerBI reports for real-time monitoring
Set up alerts - Get notified when data becomes stale

This is particularly useful for data engineers and project managers who need to ensure critical construction data is up-to-date for reporting and decision-making.

Quick Start

Get Your API Credentials

Log into Kroo

Access your Kroo application with your regular login

Navigate to Company Settings

Go to Settings > Company in the Kroo App

Copy API Credentials

Find your Basic Auth credentials (username and password) and copy them for use in API calls

Test Your Connection

Try this quick test to see your available data partners:

Windows (PowerShell)
Windows (Command Prompt)
Mac/Linux

Invoke-RestMethod -Uri 'https://api.getkroo.com/api/v1/pipeline_status/describe' `
-Method GET `
-Headers @{'Authorization' = 'Basic [YOUR_CREDENTIALS]'}

curl --location "https://api.getkroo.com/api/v1/pipeline_status/describe" ^
--header "Authorization: Basic [YOUR_CREDENTIALS]"

curl --location 'https://api.getkroo.com/api/v1/pipeline_status/describe' \
--header 'Authorization: Basic [YOUR_CREDENTIALS]'

Expected Response:

{
    "partners": [
        "procore",
        "cmic"
    ]
}

API Reference

Get Available Partners

Endpoint: GET /api/v1/pipeline_status/describe Discover which data integration partners are configured in your Kroo instance.

Get Pipeline Status

Endpoint: GET /api/v1/pipeline_status?partner={partner_name}&filters[]={pipeline_key} Retrieve the last sync timestamp for all pipelines from a specific partner. Query Parameters:

partner (required) - The name of the integration partner (e.g., “procore”, “cmic”)
filters[] (optional) - Pipeline keys to include in the response. When specified, only these pipelines will be returned. Can be specified multiple times to include multiple pipelines. If omitted, all pipelines are returned

Multiple Filters Syntax: To include multiple pipelines, repeat the filters[] parameter:

?partner=procore&filters[]=procore_vendors&filters[]=procore_offices&filters[]=procore_submittals

The [] brackets indicate an array parameter. Each repetition adds another pipeline to include.

Basic Request
With Filters
Windows (PowerShell)

curl --location 'https://api.getkroo.com/api/v1/pipeline_status?partner=procore' \
--header 'Authorization: Basic [YOUR_CREDENTIALS]'

# Include only specific pipelines in the response
curl --location 'https://api.getkroo.com/api/v1/pipeline_status?partner=procore&filters[]=procore_vendors&filters[]=procore_offices' \
--header 'Authorization: Basic [YOUR_CREDENTIALS]'

# Basic request
Invoke-RestMethod -Uri 'https://api.getkroo.com/api/v1/pipeline_status?partner=procore' `
-Method GET `
-Headers @{'Authorization' = 'Basic [YOUR_CREDENTIALS]'}

# With filters
Invoke-RestMethod -Uri 'https://api.getkroo.com/api/v1/pipeline_status?partner=procore&filters[]=procore_vendors&filters[]=procore_offices' `
-Method GET `
-Headers @{'Authorization' = 'Basic [YOUR_CREDENTIALS]'}

Sample Response:

{
    "procore_commitment_change_orders": "2025-09-07T23:02:36.395-07:00",
    "procore_vendors": "2025-09-08T07:02:21.876-07:00",
    "procore_direct_costs": "2025-09-07T21:03:10.634-07:00",
    "procore_rfis": "2025-09-07T21:03:10.634-07:00",
    "procore_submittals": "2025-09-07T20:02:38.802-07:00",
    "procore_change_order_requests": "2025-09-07T19:02:31.892-07:00",
    "procore_wbs_codes": null,
    "procore_cost_codes": null
}

Understanding the Response:

Timestamps show the last successful sync in ISO 8601 format
null values indicate pipelines that haven’t synced yet or are disabled
All times include timezone information for accurate tracking

Get Next Sync Times

Endpoint: GET /api/v1/pipeline_status/next_sync_times?partner={partner_name}&filters[]={pipeline_key} Retrieve the scheduled next sync time for all pipelines from a specific partner. This helps you anticipate when fresh data will be available. Query Parameters:

partner (required) - The name of the integration partner (e.g., “procore”, “cmic”)
filters[] (optional) - Pipeline keys to include in the response. When specified, only these pipelines will be returned. Can be specified multiple times to include multiple pipelines. If omitted, all pipelines are returned

Multiple Filters Syntax: To include multiple pipelines, repeat the filters[] parameter:

?partner=procore&filters[]=procore_submittals&filters[]=procore_departments&filters[]=procore_offices

The [] brackets indicate an array parameter. Each repetition adds another pipeline to include.

Basic Request
With Filters
Windows (PowerShell)

curl --location 'https://api.getkroo.com/api/v1/pipeline_status/next_sync_times?partner=procore' \
--header 'Authorization: Basic [YOUR_CREDENTIALS]'

# Include only specific pipelines in the response
curl --location 'https://api.getkroo.com/api/v1/pipeline_status/next_sync_times?partner=procore&filters[]=procore_submittals&filters[]=procore_departments' \
--header 'Authorization: Basic [YOUR_CREDENTIALS]'

# Basic request
Invoke-RestMethod -Uri 'https://api.getkroo.com/api/v1/pipeline_status/next_sync_times?partner=procore' `
-Method GET `
-Headers @{'Authorization' = 'Basic [YOUR_CREDENTIALS]'}

# With filters
Invoke-RestMethod -Uri 'https://api.getkroo.com/api/v1/pipeline_status/next_sync_times?partner=procore&filters[]=procore_submittals&filters[]=procore_departments' `
-Method GET `
-Headers @{'Authorization' = 'Basic [YOUR_CREDENTIALS]'}

Sample Response:

{
    "procore_coordination_issues": "2025-12-09T17:00:00.000-08:00",
    "procore_action_plans": "2025-12-09T02:00:00.000-08:00",
    "procore_schedule_tasks": "2025-12-09T03:00:00.000-08:00",
    "procore_submittals": "2025-12-09T18:00:00.000-08:00",
    "procore_departments": "2025-12-09T15:00:00.000-08:00",
    "procore_offices": "2025-12-09T18:00:00.000-08:00"
}

Understanding the Response:

Timestamps show the scheduled next sync time in ISO 8601 format
Use this to plan around data availability for time-sensitive reports
Combine with last sync times to understand the full sync schedule

PowerBI Dashboard Setup

Create a real-time pipeline monitoring dashboard in PowerBI:

Connect to the API

Open PowerBI Desktop and create a new report
Click Get Data > Web
Enter URL: https://api.getkroo.com/api/v1/pipeline_status?partner=procore
Select Basic authentication and enter your Kroo credentials

Transform the Data

In Power Query Editor:

Convert to Table - Click Convert > To Table
Expand Columns - Select Name and Value columns
Rename Columns - Change to “Pipeline” and “Last Sync Time”
Set Data Types - Text for Pipeline, Date/Time for Last Sync Time
Remove Nulls - Filter out rows with null sync times
Click Close & Apply

Build Visualizations

Create useful charts and tables:

Status Table - All pipelines with sync times
Freshness Cards - Show oldest/newest sync times
Alert Visuals - Highlight stale data (>24 hours old)
Timeline Charts - Track sync patterns over time

Enable Auto-Refresh

Publish to PowerBI Service
Go to Settings > Scheduled refresh
Set refresh frequency (hourly recommended)
Configure failure notifications

Common Use Cases

Monitoring Critical Pipelines

Set up alerts for business-critical data:

Daily Pipelines → Alert if >25 hours stale
Hourly Pipelines → Alert if >2 hours stale  
Real-time Pipelines → Alert if >30 minutes stale

Operations Dashboard

Create executive dashboards showing:

Overall data health status
Pipeline performance trends
Integration partner reliability
Data availability for key reports

Troubleshooting Data Issues

When reports show unexpected data:

Check pipeline status to identify sync delays
Compare sync times across related pipelines
Coordinate with Kroo support using specific pipeline names and timestamps

Pro Tip: Bookmark your PowerBI dashboard and check it before running important reports to ensure you’re working with fresh data.

Monitoring & Maintenance

​Overview

​Quick Start

​Get Your API Credentials

​Test Your Connection

​API Reference

​Get Available Partners

​Get Pipeline Status

​Get Next Sync Times

​PowerBI Dashboard Setup

​Common Use Cases

​Monitoring Critical Pipelines

​Operations Dashboard

​Troubleshooting Data Issues

Overview

Quick Start

Get Your API Credentials

Test Your Connection

API Reference

Get Available Partners

Get Pipeline Status

Get Next Sync Times

PowerBI Dashboard Setup

Common Use Cases

Monitoring Critical Pipelines

Operations Dashboard

Troubleshooting Data Issues