Wer liefert was (WLW) Company Scraper

Automate customer-defined searches on WLW (werliefertwas.de) and return matching supplier and company listings as clean, structured data.

Choose the search query, country, geographic filters, verification status, and number of result pages to process. The Actor then retrieves the matching public company information and returns strongly typed records suitable for research, enrichment, analytics, and automation workflows.

Each result retains WLW source identifiers and provenance information so records can be traced back to their source.

---

🚀 Built for structured supplier research

The Actor focuses on turning specific WLW searches into consistent, machine-readable company records.

• Customer-defined search scope You choose the query, region, filters, geographic scope, and maximum number of result pages for every run.

• One company = one row Results are deduplicated at company level using WLW's stable company identifiers.

• Structured company information Retrieve available business addresses, websites, contact channels, supplier classifications, company size information, and other public profile metadata.

• Product and service information Portfolio names and keywords make it easier to understand and classify what each matching company offers.

• Source provenance WLW identifiers and source references are retained in the output so downstream systems can trace records back to their origin.

• Designed for unattended runs Rate limiting, retries, schema validation, and tolerant parsing help runs continue reliably when individual records are incomplete or transient failures occur.

• Clean exports Results work directly with JSON, CSV, Excel, and Apify's table and API interfaces.

---

🎯 Typical use cases

• Supplier Discovery – Find manufacturers, distributors, and service providers matching defined criteria
• Procurement Research – Identify potential vendors within a market or geographic area
• Market Mapping – Analyze companies operating in a particular niche, region, or supplier category
• Company Research – Collect structured public information about businesses returned by a WLW search
• Data Enrichment – Supplement existing company records with public business and portfolio information
• Workflow Automation – Feed customer-defined search results into internal tools, analytics pipelines, CRMs, or other systems

The Actor processes only the search scope selected by the user for each run.

---

⚙️ Input

Every run is explicitly scoped by its input parameters.

Parameter	Type	Description
query	string	Search term to use for the WLW search. Required.
region	string	Optional country filter using an alpha-2 country code such as DE, FR, or IT.
verifiedOnly	boolean	If enabled, return only companies marked as verified by WLW.
maxPages	integer	Maximum number of search-result pages to process for this run. Required and prefilled with 1.
latitude	string	Optional latitude for a geographic search.
longitude	string	Optional longitude for a geographic search.
radius	string	Optional radius used when both latitude and longitude are supplied.

Geographic filtering

Geographic filtering is applied only when both latitude and longitude are provided.

When coordinates are supplied without an explicit radius, the Actor uses a radius of 50km.

Available radius values are:

• 10km
• 25km
• 50km
• 75km
• 100km
• 125km
• 250km

Example:

{
  "query": "CNC machining",
  "region": "DE",
  "verifiedOnly": false,
  "maxPages": 3,
  "latitude": "48.1372",
  "longitude": "11.5756",
  "radius": "50km"
}

In this example, the customer has explicitly requested at most three pages of matching results.

---

📦 Output

Each dataset row represents one unique company returned by the requested WLW search.

The output is strongly typed and designed to work both as a flat dataset and as a richer nested structure for integrations.

⭐ Common fields

• name
• website
• email
• phone
• address
• address_city
• address_countryCode
• tags_supplierTypes
• tags_employeeCount
• portfolio_productNames
• portfolio_productKeywords

Availability depends on the information exposed by the corresponding WLW listing.

---

📘 Output structure

🔹 Source and provenance

Each record contains identifiers derived from the corresponding WLW result, including where available:

• source – Always "wlw"
• source_companyId – Stable WLW company identifier
• source_listingId – Listing-level identifier
• source_epId
• source_epSlug
• source_uuid
• source_slug
• source URL / listing URL where available

These fields are retained for traceability, deduplication, and provenance.

---

🔹 Core company information

• name – Company name
• shortName – Short or alternative company name
• description – Public company-profile description
• logoUrl – Company logo URL where available

---

🔹 Location

• address – Complete formatted address
• address_street
• address_postalCode
• address_city
• address_countryCode
• geo_latitude
• geo_longitude

The flattened address fields are intended to make filtering and spreadsheet workflows straightforward.

---

🔹 Contact information

Where publicly available:

• website
• email
• phone

---

🔹 Business classification

• tags_supplierTypes – Supplier or business-type classifications
• tags_employeeCount – Employee-count or company-size information
• tags_distributionArea – Geographic distribution or service-area information

These fields can be used for filtering, categorization, and analysis of matching companies.

---

🔹 Company signals

Depending on availability:

• signals_isCustomer
• signals_certificatesCount
• signals_responseRate
• signals_averageResponseTime
• signals_foundingYear
• signals_packageName

These values reflect metadata exposed for the corresponding WLW company record.

---

🔹 Products and portfolio

The Actor can return both flattened portfolio summaries and structured product records.

Summary fields include:

• portfolio_productCount
• portfolio_productNames
• portfolio_productKeywords

Structured entries are available through:

• portfolio_products[]

Each portfolio product can contain:

• name
• description
• keywords
• WLW source identifiers
• matching/showcase flags
• associated image URLs and captions

---

🔹 Media

Company media can be returned through media[].

Entries can contain:

• url
• title
• description

---

🔹 Run metadata

Where present:

• meta.scrapedAt – Timestamp at which the record was retrieved
• meta.query – Search query supplied for the run

---

🔍 About result counts

WLW may display approximate result totals in its own interface.

The Actor deduplicates results using WLW's company identifiers, so the final number of emitted records may differ from WLW's displayed estimate.

Each emitted row represents one unique company encountered within the result pages selected for that run.

---

🛡️ Reliability and schema guarantees

The Actor is built around a validated and stable output structure.

• Strongly typed output
• Company-level deduplication
• Automatic retries for transient failures
• Rate-limited requests
• Graceful handling of missing optional fields
• Tolerant processing when individual records change shape

Because WLW profiles vary, optional fields may not be present for every company.

When the source structure changes, the Actor is updated to continue emitting consistent records where possible.

---

👥 Intended users

The Actor is suitable for:

• Procurement Teams – Research suppliers and potential vendors
• Researchers and Analysts – Study companies, sectors, and regional markets
• Agencies – Perform customer-specific business research and enrichment
• Business Owners – Identify and compare potential suppliers or commercial partners
• Sales Operations Teams – Research companies matching defined business criteria
• Automation Builders – Integrate customer-defined WLW searches into larger workflows

---

⚖️ Responsible use

This Actor provides software for automating user-defined searches against publicly accessible information.

Users determine the query, filters, geographic scope, and maximum number of result pages processed during each run.

Users are responsible for ensuring that their use of the Actor and resulting data complies with applicable laws, contractual obligations, and third-party rights.

Do not use the Actor to access content requiring authentication or other access controls.

---

💬 Support

Questions, edge cases, or unexpected results?

Open a support ticket and include the affected run ID or relevant log output so the issue can be reproduced and investigated.