# Earnings Calendar Change Monitor (`junipr/earnings-calendar-change-monitor`) Actor

Monitor public earnings calendar changes, date shifts, and event schedule updates.

- **URL**: https://apify.com/junipr/earnings-calendar-change-monitor.md
- **Developed by:** [junipr](https://apify.com/junipr) (community)
- **Categories:** Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.50 / 1,000 target checkeds

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Earnings Calendar Change Monitor

Compare two earnings calendars and return company-level additions, removals, date shifts, market-session changes, confirmation changes, estimate updates, and webcast-link updates.

### Supported Sources

Each comparison can use:

- CSV, TSV, semicolon-delimited, or pipe-delimited calendar text
- JSON arrays or objects containing `events`, `earnings`, `results`, or `data`
- Structured `previousEvents` and `currentEvents` arrays
- Simple text statements containing a ticker and ISO date
- A public current-calendar URL when `fetchUrls` is enabled

The actor normalizes common aliases for ticker, company, date, session, timezone, confirmation status, fiscal period, EPS estimate, revenue estimate, and webcast URL. Events are keyed by ticker and fiscal period, then deduplicated before comparison.

### Example Input

```json
{
  "targets": [
    {
      "sourceId": "technology-earnings",
      "sourceUrl": "https://example.com/calendars/earnings.csv",
      "previousSnapshot": "Ticker,Company,Earnings Date,Session,Status,Fiscal Quarter\nACME,Acme Cloud,2026-07-20,AMC,estimated,Q2 2026\nBRIO,Brio Retail,2026-07-22,BMO,estimated,Q2 2026",
      "currentSnapshot": "Ticker,Company,Earnings Date,Session,Status,Fiscal Quarter\nACME,Acme Cloud,2026-07-23,AMC,confirmed,Q2 2026\nBRIO,Brio Retail,2026-07-22,BMO,confirmed,Q2 2026\nNOVA,Nova AI,2026-07-25,AMC,estimated,Q2 2026"
    }
  ],
  "maxTargets": 1,
  "maxEventsPerTarget": 500,
  "includeUnchanged": false,
  "includeReport": true
}
```

### Output

Each dataset row contains:

- Source and billing fields: `rowId`, `sourceId`, `sourceUrl`, `sourceType`, `checkedAt`, `pricingEventName`
- Event identity: `eventKey`, `ticker`, `companyName`, `fiscalQuarter`
- Schedule comparison: `oldEarningsDate`, `newEarningsDate`, `dateShiftDays`, old/new market session, and old/new timezone
- Detail comparison: old/new confirmation status, EPS estimate, revenue estimate, and webcast URL
- Decision fields: `changeType`, `status`, `severity`, `score`, `summary`, and `recommendation`

`changeType` is `added`, `removed`, `date-shifted`, `time-shifted`, `status-changed`, `details-changed`, or `unchanged`.

Failed fetches and calendars with no valid events produce an explicit diagnostic row through `diagnosticCode` and `sourceError`.

### Example Output

```json
{
  "ticker": "ACME",
  "companyName": "Acme Cloud",
  "fiscalQuarter": "Q2 2026",
  "oldEarningsDate": "2026-07-20",
  "newEarningsDate": "2026-07-23",
  "dateShiftDays": 3,
  "oldTimeOfDay": "after-market-close",
  "newTimeOfDay": "after-market-close",
  "oldStatus": "estimated",
  "newStatus": "confirmed",
  "changeType": "date-shifted"
}
```

### PPE Pricing

Event prices include Apify platform usage for the configured fixed-inclusive model.

- `actor-start`: $0.02000 once per paid run
- `target-checked`: $0.00650 per calendar target
- `snapshot-compared`: $0.00650 per comparison
- `change-detected`: $0.01300 per emitted change
- `digest-generated`: $0.05000 when digest artifacts are written
- `executive-report-generated`: $0.10000 when the Markdown report is written

The actor stops before additional output when the charge limit cannot cover the next paid event.

### Limits

- Up to 50 calendar targets and 5,000 events per side per target.
- Plain-text parsing intentionally supports only clear ticker plus ISO-date statements. Use CSV, JSON, or structured records for richer sources.
- A fetched current calendar still needs a supplied previous calendar for comparison.
- Calendar data can change quickly. Confirm material changes against current issuer announcements.

# Actor input Schema

## `targets` (type: `array`):

Capped previous/current calendar comparisons.

## `sourceUrl` (type: `string`):

Public URL fetched as the current calendar when enabled.

## `previousSnapshot` (type: `string`):

Previous CSV, JSON, or text calendar.

## `currentSnapshot` (type: `string`):

Current CSV, JSON, or text calendar.

## `previousEvents` (type: `array`):

Previous structured earnings events.

## `currentEvents` (type: `array`):

Current structured earnings events.

## `fetchUrls` (type: `boolean`):

Fetch sourceUrl only when currentSnapshot is omitted.

## `fetchTimeoutMs` (type: `integer`):

Per-request timeout in milliseconds.

## `maxTargets` (type: `integer`):

Maximum calendar comparisons.

## `maxEventsPerTarget` (type: `integer`):

Maximum events read from each side.

## `maxTextBytes` (type: `integer`):

Maximum bytes retained for each snapshot.

## `includeUnchanged` (type: `boolean`):

Emit events with no comparable changes.

## `includeReport` (type: `boolean`):

Write results JSON, summary JSON, and Markdown digest.

## `dryRun` (type: `boolean`):

Validate input without paid output.

## `debug` (type: `boolean`):

Enable debug logging.

## Actor input object example

```json
{
  "targets": [],
  "sourceUrl": "",
  "previousSnapshot": "",
  "currentSnapshot": "",
  "previousEvents": [],
  "currentEvents": [],
  "fetchUrls": false,
  "fetchTimeoutMs": 10000,
  "maxTargets": 1,
  "maxEventsPerTarget": 500,
  "maxTextBytes": 120000,
  "includeUnchanged": false,
  "includeReport": true,
  "dryRun": false,
  "debug": false
}
```

# Actor output Schema

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

Normalized event changes.

## `resultsJson` (type: `string`):

All changed events as JSON.

## `summary` (type: `string`):

Change counts and truncation state.

## `markdownReport` (type: `string`):

Readable earnings schedule change digest.

# 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("junipr/earnings-calendar-change-monitor").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("junipr/earnings-calendar-change-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).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 junipr/earnings-calendar-change-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=junipr/earnings-calendar-change-monitor",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/2ZH3M0Zbk3U6tc6WT/builds/aADMpcoifA38ZogA8/openapi.json