# CER Pipeline Incidents – Canada Energy Regulator (`loudtzu/cer-pipeline-incidents`) Actor

Incidents on federally regulated Canadian pipelines from CER open data: company, substance, volume, cause, location, injuries/fatalities counts.

- **URL**: https://apify.com/loudtzu/cer-pipeline-incidents.md
- **Developed by:** [Travis M](https://apify.com/loudtzu) (community)
- **Categories:** Business, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## CER Pipeline Incidents – Canada Energy Regulator

### What it does

Reads the Canada Energy Regulator's **comprehensive pipeline incident** CSV, covering incidents on federally regulated pipelines since 2008 (~2,000 incidents, updated monthly). It returns clean, filtered records: company, substance, volume released, cause categories, location, significance, and injury, fatality and evacuation counts. One file download per run, no page scraping.

Source: [Pipeline Incident Data on open.canada.ca](https://open.canada.ca/data/en/dataset/7dffedc4-23fa-440c-a36d-adf5a6cc09f1).

### Who it's for

Energy and ESG analysts, insurers and risk teams, environmental groups, journalists and researchers comparing operators, substances and causes.

### Input

| Key | Notes |
|---|---|
| `company` | contains, e.g. `Enbridge` |
| `province` | contains, e.g. `Alberta` |
| `substance` | contains, e.g. `Crude Oil`, `Natural Gas` |
| `incidentType` | contains, e.g. `Release of Substance`, `Fire` |
| `significantOnly` | only incidents CER flags as significant |
| `minVolumeM3` | minimum approximate volume released |
| `reportedFrom` / `reportedTo` | YYYY-MM-DD |
| `maxItems` | default 100, maximum 50,000 |

Example: `{"substance": "Crude", "reportedFrom": "2024-01-01"}`

### Output

`incidentNumber`, `incidentTypes`, `reportedDate`, `occurrenceDateTime` (as published, local time with zone name), `year`, `status`, `closedDate`, `company`, `province`, `nearestPopulatedCentre`, `latitude`, `longitude`, `substance`, `releaseType`, `volumeReleasedM3`, `significant`, `whatHappenedCategory`, `whatHappened`, `whyHappenedCategory`, `whyHappened`, `pipelineOrFacilityType`, `pipelineName`, `facilityName`, `fatalities`, `injured`, `evacuated`, `source`, `licence`. Dates are converted to YYYY-MM-DD.

### Privacy

- Per-person injury detail is **not exported**: `Type of Injury`, `Activity at time of fatality`, `Workdays lost` and `Work restricted by injury` are dropped. Only the counts (fatalities, injured, evacuated) are kept.
- In the detail text fields, every email address and phone number is replaced with `[redacted]` (none were found in the Oct 2026 file).
- What is checked: the four per-person injury columns above are dropped; `whatHappened` and `whyHappened` (free text) are scanned and email addresses and phone numbers replaced. No other field is scanned for personal names, and the free text is not name-filtered. `company` is the regulated operator. Only the fields listed under Output are exported. Latitude and longitude are the incident location on the pipeline, as published by CER.
- The data is **reduced, not anonymous**: an incident's date, place and counts may still let someone who knows the event identify the people involved.
- The other ~75 technical columns (pipe specs, pressures and so on) are not included in v0.1.

### Licence and terms

- **Licence:** [Open Government Licence – Canada](https://open.canada.ca/en/open-government-licence-canada), which allows use "including for commercial purposes" with attribution. Every row carries the attribution.
- **Automated access:** `www.cer-rec.gc.ca/robots.txt` disallows only `/fracfocus` and `/bin` for general crawlers (plus a list of named bad bots), and `/open/` is allowed. No terms were found that ban automated download of the open data. The Actor makes one request per run.
- Independent; not endorsed by the Canada Energy Regulator.

### Pricing

**Price: $0.003 per result, no start fee** (pay per event `apify-default-dataset-item`, one result = one incident). The full ~2,000 incidents cost about $6.

### Limits

- English file only. The data is as current as CER's monthly update. Recent incidents may still show "Submitted" status and change later.

# Actor input Schema

## `company` (type: `string`):

e.g. Enbridge, TC Energy.

## `province` (type: `string`):

e.g. Alberta.

## `substance` (type: `string`):

e.g. Crude Oil, Natural Gas.

## `incidentType` (type: `string`):

e.g. Release of Substance, Fire, Explosion.

## `significantOnly` (type: `boolean`):

Only incidents CER flags as significant.

## `minVolumeM3` (type: `integer`):

Optional.

## `reportedFrom` (type: `string`):

YYYY-MM-DD

## `reportedTo` (type: `string`):

YYYY-MM-DD

## `maxItems` (type: `integer`):

Stop after this many items (1–50,000, default 100).

## Actor input object example

```json
{
  "significantOnly": false,
  "maxItems": 100
}
```

# Actor output Schema

## `results` (type: `string`):

All items returned by the run, in the 'overview' table view.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("loudtzu/cer-pipeline-incidents").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("loudtzu/cer-pipeline-incidents").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call loudtzu/cer-pipeline-incidents --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,loudtzu/cer-pipeline-incidents"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/mDQtlFXdccQ0XCHdw/builds/bjc6v1R9Yqkar9pQg/openapi.json