Messe Frankfurt Exhibitor List Scraper

Scrape public Messe Frankfurt exhibitor-search pages into clean company lead records.

The actor is designed for sales teams, agencies, sponsors, logistics providers, market researchers, and event operations teams that need structured exhibitor data from Messe Frankfurt fair websites such as Ambiente.

What does this actor do?

It reads Messe Frankfurt exhibitor search pages, discovers the public fair identifier used by the website, calls the same public exhibitor API used by the page, and saves each exhibitor as a structured dataset item.

You can collect company names, profile URLs, hall and stand information, countries, cities, addresses, contact fields where available, product categories, keywords, and timestamps.

Why use it?

Messe Frankfurt exhibitor lists are valuable for lead generation and event planning, but copying them manually is slow and error-prone.

This actor automates that workflow and gives you export-ready data for spreadsheets, CRMs, BI tools, or enrichment pipelines.

Typical use cases

• Build exhibitor lead lists before a trade fair.
• Segment exhibitors by country or city.
• Plan booth visits by hall and stand.
• Find potential distributors, partners, or suppliers.
• Prepare outreach campaigns for event sponsors.
• Monitor which companies participate in a fair.
• Enrich internal account lists with event-presence signals.

Supported websites

The default input targets Ambiente:

https://ambiente.messefrankfurt.com/frankfurt/en/exhibitor-search.html

Other Messe Frankfurt exhibitor-search pages with the same public search component can be used through startUrls.

Input options

Exhibitor search URLs

Add one or more Messe Frankfurt exhibitor-search page URLs. The actor discovers the fair ID and language from each page.

Fair IDs

Advanced users can pass Messe Frankfurt fair IDs directly, for example AMBIENTE. If this field is set, URL discovery is skipped.

Search query

Use query to filter by company, product, category, or related text supported by the source website.

Maximum exhibitors

Use maxItems to control the run size and cost.

Page size

Use pageSize to control API pagination. The actor caps this to a safe value.

Fetch profile details

Enable includeDetails when you need richer descriptions, categories, and contact details from exhibitor profile endpoints.

Request delay

Use delayMs to slow down large runs, especially with detail enrichment enabled.

Example input

{
  "startUrls": [
    { "url": "https://ambiente.messefrankfurt.com/frankfurt/en/exhibitor-search.html" }
  ],
  "maxItems": 100,
  "pageSize": 50,
  "includeDetails": false,
  "delayMs": 100
}

Example query input

{
  "startUrls": [
    { "url": "https://ambiente.messefrankfurt.com/frankfurt/en/exhibitor-search.html" }
  ],
  "query": "furniture",
  "maxItems": 50,
  "includeDetails": true
}

Output fields

Each dataset item represents one exhibitor.

Field: fairId

The Messe Frankfurt fair identifier, for example AMBIENTE.

Field: fairName

The public event or fair name returned by the source.

Field: eventStartDate

The fair start date when available.

Field: eventEndDate

The fair end date when available.

Field: exhibitorId

The source exhibitor ID.

Field: rewriteId

The source profile slug used in Messe Frankfurt profile URLs.

Field: exhibitorName

The exhibitor or company name.

Field: description

A plain-text profile description when available.

Field: profileUrl

A link to the public Messe Frankfurt exhibitor profile.

Field: hall

The hall value returned by the fair website.

Field: stand

The booth or stand value returned by the fair website.

Field: hallStand

A combined hall and stand field for quick spreadsheet filtering.

Field: country

The exhibitor country name.

Field: countryCode

The source country code, usually ISO-3 when available.

Field: city

The exhibitor city.

Field: zip

The postal code.

Field: street

The street address.

Field: phone

The public phone number when available.

Field: fax

The public fax number when available.

Field: email

The public email address when available.

Field: website

The public website URL when available or detected in the profile text.

Field: productCategories

A list of product category names associated with the exhibitor.

Field: keywords

Keywords returned by the source profile.

Field: productsCount

Number of products listed by the source profile when available.

Field: sourceUrl

The input page used to discover or represent the fair.

Field: scrapedAt

ISO timestamp for when the record was saved.

Data quality notes

The actor returns data that is publicly available on Messe Frankfurt websites. Some exhibitors do not publish emails, websites, phone numbers, or complete addresses. Those fields will be null when the source does not provide them.

Detail enrichment notes

The search API already returns useful exhibitor records. Enabling includeDetails fetches each profile individually and can improve descriptions, categories, and contact fields.

For large runs, start without detail enrichment, then enable it if you need richer profiles.

Pagination

The actor keeps requesting pages until it reaches maxItems, the source returns no more results, or the current fair is complete.

Cost control

Set maxItems to a small value for first tests. Increase it after confirming the output matches your workflow.

Responsible use

Use this actor for legitimate business research, event planning, and lead preparation. Respect applicable privacy, marketing, and anti-spam laws when using contact data.

Tips for CRM import

Export the dataset as CSV or Excel. Use exhibitorName, website, email, and country for deduplication and enrichment.

Tips for booth planning

Sort by hallStand, then group by country or productCategories to prepare route plans.

Tips for market research

Use productCategories and keywords to identify segments represented at a fair.

Limitations

The actor depends on the current Messe Frankfurt public exhibitor-search API. If Messe Frankfurt changes its frontend or API contract, the actor may require an update.

Troubleshooting

If a run returns fewer records than expected, check maxItems, query, and whether the source fair currently has published exhibitors.

FAQ: Can I scrape multiple fairs?

Yes. Add multiple exhibitor search URLs or pass multiple fair IDs.

FAQ: Does it require login?

No. It uses public exhibitor data exposed by the fair website.

FAQ: Does it scrape private attendee data?

No. It extracts public exhibitor/company information.

FAQ: Can I use the API directly?

Yes. Run the actor through Apify API and download the default dataset.

Output example

{
  "fairId": "AMBIENTE",
  "fairName": "Ambiente 2026",
  "exhibitorName": "Example GmbH",
  "hallStand": "3.0, G32",
  "country": "Germany",
  "city": "Frankfurt am Main",
  "email": "info@example.com",
  "website": "https://www.example.com",
  "productCategories": ["Interior Design"],
  "sourceUrl": "https://ambiente.messefrankfurt.com/frankfurt/en/exhibitor-search.html"
}

Changelog

Initial version: HTTP-first Messe Frankfurt exhibitor extraction with optional profile enrichment.

Who is it for?

This actor is for sales development teams, event sponsors, booth-service vendors, logistics providers, trade-fair consultants, distributors, sourcing teams, and analysts who need structured Messe Frankfurt exhibitor data instead of manual copying.

Pricing

The actor uses pay-per-event pricing. A small run-start event covers fixed startup work, and a per-exhibitor event is charged for saved exhibitor records. Use maxItems to control spend before running larger fair exports.

API usage

You can run the actor from the Apify API, Apify client libraries, or the Apify Console. Replace the token and actor ID with your own values.

API usage with Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/messe-frankfurt-exhibitor-list-scraper').call({
  startUrls: [{ url: 'https://ambiente.messefrankfurt.com/frankfurt/en/exhibitor-search.html' }],
  maxItems: 100,
  pageSize: 50,
  includeDetails: false,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

API usage with Python

from apify_client import ApifyClient

client = ApifyClient('YOUR_APIFY_TOKEN')
run = client.actor('automation-lab/messe-frankfurt-exhibitor-list-scraper').call(run_input={
    'startUrls': [{'url': 'https://ambiente.messefrankfurt.com/frankfurt/en/exhibitor-search.html'}],
    'maxItems': 100,
    'pageSize': 50,
    'includeDetails': False,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

API usage with cURL

curl -X POST 'https://api.apify.com/v2/acts/automation-lab~messe-frankfurt-exhibitor-list-scraper/runs?token=YOUR_APIFY_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"startUrls":[{"url":"https://ambiente.messefrankfurt.com/frankfurt/en/exhibitor-search.html"}],"maxItems":100,"pageSize":50,"includeDetails":false}'

MCP

If you use Apify through an MCP-enabled assistant, provide the actor ID automation-lab/messe-frankfurt-exhibitor-list-scraper and the same JSON input shown above. The assistant can start the run, wait for completion, and read the default dataset.

Add the Apify MCP server with this CLI command:

$claude mcp add apify -- npx -y @apify/actors-mcp-server --actors automation-lab/messe-frankfurt-exhibitor-list-scraper

Example MCP server JSON config:

{
  "mcpServers": {
    "apify": {
      "command": "npx",
      "args": ["-y", "@apify/actors-mcp-server", "--actors", "automation-lab/messe-frankfurt-exhibitor-list-scraper"],
      "env": { "APIFY_TOKEN": "YOUR_APIFY_TOKEN" }
    }
  }
}

MCP example prompts:

Example prompts for MCP usage:

• "Use the Apify MCP server to run the Messe Frankfurt Exhibitor List Scraper for Ambiente and return 100 exhibitors."
• "Use MCP to find design-related Ambiente exhibitors and summarize their booth locations."
• "Use the MCP actor tool to export Messe Frankfurt exhibitor leads with websites and emails as CSV-ready dataset rows."

Legality

This actor collects public exhibitor/company information exposed on Messe Frankfurt websites. It does not bypass login pages or collect private attendee data. You are responsible for using exported contact data lawfully, including complying with marketing, privacy, and anti-spam rules in your jurisdiction.

MCP setup

You can connect Apify to an MCP-compatible desktop assistant and run this actor from natural-language prompts.

MCP CLI add command

$claude mcp add apify -- npx -y @apify/actors-mcp-server --actors automation-lab/messe-frankfurt-exhibitor-list-scraper

MCP JSON config

{
  "mcpServers": {
    "apify": {
      "command": "npx",
      "args": [
        "-y",
        "@apify/actors-mcp-server",
        "--actors",
        "automation-lab/messe-frankfurt-exhibitor-list-scraper"
      ],
      "env": {
        "APIFY_TOKEN": "YOUR_APIFY_TOKEN"
      }
    }
  }
}

MCP example prompts

• "Run the Messe Frankfurt Exhibitor List Scraper for Ambiente and return the first 100 exhibitors."
• "Find Ambiente exhibitors matching design and summarize their countries and booth locations."
• "Export Messe Frankfurt exhibitor leads with websites and emails to a dataset I can download as CSV."

MCP workflow tip

Ask your MCP assistant to run a small maxItems test first. After you confirm the fields, increase maxItems for the full exhibitor export.