# MunchEye Launch Calendar Scraper | JVZoo & WarriorPlus Launches (`tactful_anvil/muncheye-launch-calendar-scraper`) Actor

Scrape every IM product launch on MunchEye: vendor, product, launch date, front-end price, affiliate commission %, network (JVZoo, WarriorPlus, Launchpad), big-launch flag, est. commission per sale and a 0-100 launch score. HTTP-only, no login, schedule-ready.

- **URL**: https://apify.com/tactful\_anvil/muncheye-launch-calendar-scraper.md
- **Developed by:** [Mr Zack](https://apify.com/tactful_anvil) (community)
- **Categories:** Lead generation, Automation, E-commerce
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.80 / 1,000 launch 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?

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

## MunchEye Launch Calendar Scraper — JVZoo & WarriorPlus Launches

Every serious affiliate in the "internet marketing" space checks [MunchEye](https://muncheye.com/) — the public JV launch calendar — to decide which product launches to promote next. Launches pay **50-75% front-end commission** plus JV contest prizes, and the launch window is everything: build your bonus page and email sequence *before* launch day, or watch the leaderboard without you on it.

This actor turns that daily manual check into structured data: **one run returns every listed launch** (~600 at the time of writing) across **WarriorPlus, JVZoo, Launchpad, ClickBank and Explodely**, with the numbers you actually pick launches by.

### Who this is for

- **Affiliate marketers** planning their promo calendar: filter to launches in the next 14 days paying ≥50% on a ≥$27 front-end.
- **Bonus-page & email-sequence builders** who prep assets per launch and need lead time.
- **JV managers & vendors** watching what's launching against them in their niche and week.
- **Newsletter / community operators** (launch roundups, "what's launching this week" posts) who want the data without the copy-paste.

### Output fields

| Field | Meaning |
|---|---|
| `productName`, `vendor` | Parsed from the listing ("Vendor: Product"). |
| `network` | WarriorPlus, JVZoo, Launchpad, Clickbank, Explodely. |
| `launchDate`, `daysToLaunch` | ISO date from the board's own structured data; negative = already launched. |
| `status` | `upcoming`, `today`, `launched`, `parked` (placeholder slot years out), `unknown`. |
| `priceRaw`, `priceUsd` | Front-end price as published + parsed USD (null when not published — never a fake 0). |
| `commissionPct` | Affiliate commission % as published. |
| `estCommissionUsd` | Front-end price × commission % = what one front-end sale pays you. Upsells/bundles not included — treat it as a floor. |
| `isBigLaunch` | Featured in MunchEye's **Big Launches** list (heaviest JV push). |
| `launchScore` | 0-100: launch window 40 + est. commission 30 (log-scaled) + big-launch 20 + network 10. Unknown data scores neutral, never bonus. |
| `muncheyeUrl` | The launch's detail page (JV page link, prizes, launch time). |

### How to schedule this actor (this is the whole point)

The calendar moves every day — new launches appear, dates shift, big launches get announced. A launch you spot 10 days early is a promo; one you spot on launch day is a missed leaderboard.

1. Open the actor → **Schedules** → create a schedule (daily at your morning hour works well).
2. Recommended input for a promo-planning feed: `status: "upcoming"`, `maxDaysToLaunch: 21`, `sortBy: "launchDate"`.
3. Add an integration (email, Slack, webhook, Google Sheets) so each morning's run lands where you plan your promos.
4. Diff tip: keep `sortBy: "launchDate"` and compare against yesterday's dataset — new slugs = new launches announced.

### Honest limitations

- Data comes from MunchEye's public board; if a vendor doesn't list there, we can't see it.
- `estCommissionUsd` covers the front-end only. Real EPCs with upsells are typically higher — check the JV page (`muncheyeUrl`) for the full funnel.
- Some rows are placeholders ("TBA", parked far-future dates). We flag them (`status: "parked"`, null prices) instead of guessing.
- Launch *time* (e.g. 11am EST) and JV page URL live on the detail pages, not the board — this actor stays one-request cheap by design.

### Was this Actor useful?

If it saved you the daily board-checking routine, a review on the Store page helps more people find it. Something broken or missing a field you need? Open an issue in the **Issues** tab — I ship fixes fast.

# Actor input Schema

## `status` (type: `string`):

'upcoming' = launches that have not happened yet (incl. today) — the default affiliates want. 'launched' = already live. 'all' = everything on the board (incl. parked far-future placeholder slots).

## `networks` (type: `array`):

Only launches on these networks. Leave empty for all (WarriorPlus, JVZoo, Launchpad, ClickBank, Explodely).

## `bigLaunchesOnly` (type: `boolean`):

Only launches featured in MunchEye's Big Launches list (heaviest JV push, biggest prize pools).

## `minPriceUsd` (type: `integer`):

Keep launches whose front-end price is at least this many USD. Rows with no published price are dropped when set.

## `minCommissionPct` (type: `integer`):

Keep launches paying at least this affiliate commission percentage. Rows with no published commission are dropped when set.

## `maxDaysToLaunch` (type: `integer`):

Only launches happening within N days from now — promo-planning window mode.

## `searchText` (type: `string`):

Case-insensitive match against vendor + product name.

## `sortBy` (type: `string`):

Order of the result rows.

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

Cap on rows pushed to the dataset (billing cap).

## Actor input object example

```json
{
  "status": "upcoming",
  "networks": [],
  "bigLaunchesOnly": false,
  "sortBy": "launchDate",
  "maxItems": 1000
}
```

# Actor output Schema

## `launches` (type: `string`):

One row per listed internet-marketing product launch: vendor, product, launch date + days to launch, network, front-end price, affiliate commission %, est. commission per sale, big-launch flag and a 0-100 launch score.

# 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("tactful_anvil/muncheye-launch-calendar-scraper").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("tactful_anvil/muncheye-launch-calendar-scraper").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 tactful_anvil/muncheye-launch-calendar-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,tactful_anvil/muncheye-launch-calendar-scraper"
        }
    }
}

```

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/48MMzKcRob2vJlusd/builds/kjiXs1tjeLJpnasRx/openapi.json