# Saudi Build Exhibitor Directory (`vixendata/saudi-build-exhibitor-directory`) Actor

Extract public Saudi Build exhibitor companies, stands, sectors, products, countries and websites from its official directory, with edition caveats.

- **URL**: https://apify.com/vixendata/saudi-build-exhibitor-directory.md
- **Developed by:** [Vixendata](https://apify.com/vixendata) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 company/stand/edition records

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

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 examples already wired to this Actor's own input schema, see the [API](#api) section below.

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

# README

## Saudi Build Exhibitor Directory

Turn the public Saudi Build exhibitor list into company-and-stand records for supplier research and event preparation. Export company names, stands, sectors, products, countries, company websites and published descriptions to JSON, CSV or Excel through the Apify dataset.

### Quick start

Run with `{"maxCompanies":100}`. The only input, `maxCompanies`, is a hard output cap from 1 to 1,000 (default 100). A two-company hosted smoke test uses `{"maxCompanies":2}`. Empty fields remain null.

### What you get

Each row includes `companyName`, `stand`, `sector`, `products`, `country`, `website`, `description`, `eventName`, `eventEdition`, `editionEvidence`, `sourceId`, `sourceRowId`, `sourceUrl` and UTC `fetchedAt`. Sector and product lists preserve the site's punctuation instead of guessing category boundaries. Websites are unwrapped from Google redirect links but never visited. `sourceId` hashes normalized company name, stand and observed edition; distinct stands stay distinct. The site's positional row number is also retained, but is not used as a stable identity.

### Coverage and freshness

Source: https://saudi-build.com/exhibitors-list/

The verified page contains the entire public table, including expandable details, in one HTML response. A research snapshot contained 168 raw rows, including 50 blank placeholders and 118 named company-and-stand records. It is not a directory of every Saudi company. No invented pagination or detail-page requests are used. Descriptions, websites and categories are absent for some exhibitors.

`eventEdition` is populated only when the company descriptions explicitly mention one unambiguous “Saudi Build YYYY” edition. The observed source contains explicit Saudi Build 2026 references; the value is derived from source text, never the current date or an assumed upcoming edition. It is attribution of the current public list, not independently verified participation or a historical comparison. Conflicting or absent year evidence yields null. `OUTPUT` in the key-value store reports raw, blank, deduplicated and exported counts and whether the output cap truncated the list.

### Safe, bounded operation

The Actor fetches robots.txt and one public directory page, respects robots disallows and crawl delays, restricts redirects to the same exact source paths, and stops on access restrictions (401/403/429), challenge pages, changed columns or missing content. No proxies, accounts, CAPTCHA solving or access-control workarounds. No schedules or monitoring are created. It extracts public business prose, not individual contact fields; company claims are not independently verified. Missing content is never synthesized.

### Development

Python 3.12. Install requirements.txt, then run `python -m src`. The runtime pins Apify 4.0.2, Crawlee 1.10.4 and Pydantic 2.13.5. Table parsing and HTTP use the Python standard library; Protego 0.7.0 handles robots groups and pacing. Run offline tests with `python -m unittest discover -s tests -v`; metadata tests additionally use jsonschema 4.26.0. Sanitized fixtures preserve genuine table markup and remove unrelated page tracking/navigation. Local live testing incurs no Apify run charge. Hosted operation is a separately approved, private bounded smoke test; deployment does not publish a Store listing.

# Actor input Schema

## `maxCompanies` (type: `integer`):

Hard cap on unique company-and-stand rows exported from the public directory.

## Actor input object example

```json
{
  "maxCompanies": 100
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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("vixendata/saudi-build-exhibitor-directory").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("vixendata/saudi-build-exhibitor-directory").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 vixendata/saudi-build-exhibitor-directory --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,vixendata/saudi-build-exhibitor-directory"
        }
    }
}
```

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/rlCTs6o3qebJUL2cP/builds/1b72kc32Ql4jWynZd/openapi.json