# IFA Berlin Exhibitor Links Scraper (`outspoken_strategy/ifa-berlin-links-scraper`) Actor

Collects all exhibitor detail-page URLs from ifa-berlin.com/exhibitors, including card metadata (name, logo, categories, hall/stand locations, country). Auto-detects the last pagination page so it keeps working as the list grows.

- **URL**: https://apify.com/outspoken\_strategy/ifa-berlin-links-scraper.md
- **Developed by:** [code craker](https://apify.com/outspoken_strategy) (community)
- **Categories:** Automation, News, Lead generation
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.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/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

## IFA Berlin Exhibitor Links Scraper

Collects **every exhibitor detail-page URL** from
[ifa-berlin.com/exhibitors](https://www.ifa-berlin.com/exhibitors), plus all
the metadata visible on each listing card. Designed as **stage 1** of a
two-stage pipeline — its output dataset feeds the detail scraper that visits
each exhibitor page.

### What it does

1. Loads the exhibitor list and reads the pagination to find the **current
   last page** (55 today, auto-adjusts as the list grows or shrinks).
2. Crawls every list page with a lightweight HTTP crawler (`CheerioCrawler`)
   through rotating Apify datacenter proxies with a session pool, so blocks
   auto-retry from a fresh IP.
3. Pushes one dataset item per unique exhibitor.

### Output item

```json
{
    "name": "Acer Inc.",
    "slug": "acer",
    "url": "https://www.ifa-berlin.com/exhibitors/acer",
    "logoUrl": "https://drive.ifa-berlin.com/drive/2025/08/_cache/....png.webp",
    "country": "Taiwan",
    "showAreas": ["Computing & Gaming"],
    "locations": [
        { "showArea": "Computing & Gaming", "hall": "CityCube Hall A", "stand": "A5" }
    ],
    "listPage": 1,
    "scrapedAt": "2026-07-09T12:00:00.000Z"
}
```

`url` and `slug` are what the detail scraper needs; the rest is a free bonus
from the cards (useful for filtering which exhibitors to deep-scrape).

### Input

| Field | Default | Notes |
| --- | --- | --- |
| `startUrl` | `https://www.ifa-berlin.com/exhibitors` | Can include filter params, e.g. `?category=8` — pagination is preserved within the filter. |
| `maxPages` | `0` (no cap) | Safety cap for test runs, e.g. `2`. |
| `maxConcurrency` | `5` | Parallel page fetches. 5 is polite and finishes ~55 pages in well under a minute. |
| `proxyConfiguration` | Apify datacenter proxy | Datacenter is sufficient for this site. |

### Run locally

```bash
cd ifa-berlin-links-scraper
npm install
apify run          # or: npm start (uses ./storage for local dataset)
```

Results land in `storage/datasets/default/`.

### Deploy

```bash
apify login        # once
apify push
```

# Actor input Schema

## `startUrl` (type: `string`):

Exhibitor list URL. You can append filter query params (e.g. ?category=8) and the scraper will paginate within that filter.

## `maxPages` (type: `integer`):

Safety cap on how many list pages to crawl. 0 = no cap (crawl every page found in the pagination).

## `maxConcurrency` (type: `integer`):

Maximum number of list pages fetched in parallel. Keep modest to stay polite.

## `proxyConfiguration` (type: `object`):

Proxy settings. Defaults to Apify datacenter proxies with IP rotation, which is enough for this site.

## Actor input object example

```json
{
  "startUrl": "https://www.ifa-berlin.com/exhibitors",
  "maxPages": 0,
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# 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 = {
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("outspoken_strategy/ifa-berlin-links-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 = { "proxyConfiguration": { "useApifyProxy": True } }

# Run the Actor and wait for it to finish
run = client.actor("outspoken_strategy/ifa-berlin-links-scraper").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 '{
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call outspoken_strategy/ifa-berlin-links-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=outspoken_strategy/ifa-berlin-links-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/5I1ETELMbeAGwrezP/builds/wEEhzIXUiJeTIpak4/openapi.json