# Check Broken Links: HTTP 200 vs 404 Example

**Use case:** 

Compare a working URL (HTTP 200) with an intentionally missing page (HTTP 404) using Affiliate Revenue Leak Monitor. This example checks two public HTTP test endpoints, classifies their responses, and exports CSV findings. It demonstrates HTTP status detection, not actual affiliate commission loss.

## Input

```json
{
  "mode": "scan",
  "pageUrls": "",
  "manualLinks": "https://httpbin.org/status/200\nhttps://httpbin.org/status/404",
  "maxPages": 2,
  "maxLinks": 2,
  "checkAllLinks": false,
  "expectedTrackingKey": "",
  "expectedTrackingValue": ""
}
```

## Output

```json
{
  "risk_level": {
    "label": "Risk level",
    "format": "text"
  },
  "http_status": {
    "label": "HTTP status"
  },
  "link_category": {
    "label": "Link category",
    "format": "text"
  },
  "link_text": {
    "label": "Link text",
    "format": "text"
  },
  "original_url": {
    "label": "Checked URL",
    "format": "link"
  },
  "risk": {
    "label": "Finding",
    "format": "text"
  },
  "recommended_action": {
    "label": "Recommended action",
    "format": "text"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The Affiliate Revenue Leak Monitor Actor is ready to run with the inputs already set for "Check Broken Links: HTTP 200 vs 404 Example". [Sign up or log in](https://console.apify.com/create-task-from-example/Hw2QrtaYIpFyl6Eo9) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Check Broken Links: HTTP 200 vs 404 Example" task

The Affiliate Revenue Leak Monitor Actor will start running based on the input automatically. You can also change all the input fields, like mode, manual links (including youtube description links), and more, to match your specific use case.

### 3. Receive the "Check Broken Links: HTTP 200 vs 404 Example" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as risk level, HTTP status, link category, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Check Broken Links: HTTP 200 vs 404 Example" task via API](https://apify.com/faithful_schlumbergera/affiliate-revenue-leak-monitor.md).

## About this Actor

This example demonstrates how to use [Affiliate Revenue Leak Monitor](https://apify.com/faithful_schlumbergera/affiliate-revenue-leak-monitor.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/faithful_schlumbergera/affiliate-revenue-leak-monitor.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

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 full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/faithful_schlumbergera/affiliate-revenue-leak-monitor.md

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`).