# GlobalSpec Supplier Scraper (`moving_beacon-owner1/globalspec-supplier-scraper`) Actor

Scrapes GlobalSpec industrial supplier and manufacturer listings by keyword or A–Z directory, returning company names, profiles, contact details, websites, business types, logos, and manufacturer/distributor status. Profile enrichment adds full company information for research and lead generation.

- **URL**: https://apify.com/moving\_beacon-owner1/globalspec-supplier-scraper.md
- **Developed by:** [Jamshaid Arif](https://apify.com/moving_beacon-owner1) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $9.99 / 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/actors/running/actors-in-store.md#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

## GlobalSpec Supplier Scraper

Collects industrial supplier and manufacturer profiles from GlobalSpec's engineering directory and returns one flat record per company. Search by product keyword to find the suppliers behind matching products, or browse the A-Z company directory one letter at a time. Each record can be enriched with the company's full profile: address, phone, fax, website, business type, logo and social links.

### Input

| Field | Default | Description |
| --- | --- | --- |
| `search_mode` | `keyword` | `keyword` finds suppliers matching a product search; `letter` browses one A-Z directory page. |
| `query` | `pressure sensors` | Product/keyword in keyword mode, or a single letter `A`-`Z` in letter mode (`1` for companies starting with a digit). |
| `limit` | `25` | Maximum supplier records to return (1-200). |
| `fetch_profiles` | `true` | Visit each supplier's profile page for full contact details (slower, one extra request per supplier). |
| `proxyConfiguration` | Optional | Enable a US-based proxy for the most reliable results. |

### Output

Each result is one supplier:

```json
{
    "source": "globalspec",
    "search_mode": "keyword",
    "query": "hydraulic pumps",
    "name": "Radwell International",
    "supplier_id": "336341",
    "profile_url": "https://www.globalspec.com/supplier/profile/RadwellInternational",
    "headquarters": "Willingboro, NJ 08046 United States",
    "address": "1 Millennium Drive, Willingboro, NJ 08046 United States",
    "address_line1": "1 Millennium Drive",
    "address_line2": "Willingboro, NJ 08046 United States",
    "phone": "(609) 288-9393",
    "fax": "(609) 288-9417",
    "website": "http://www.radwell.com/",
    "business_type": "Distributor, Service",
    "logo_url": "https://www.globalspec.com/RadwellInternational/LOGO.JPEG",
    "social_media": null,
    "online_catalog": null,
    "custom_orders": null,
    "is_manufacturer": false,
    "is_distributor": true,
    "is_service": true,
    "raw": { ... }
}
```

Letter-mode records additionally fill `online_catalog` and `custom_orders` flags from the directory table.

### Notes

- Runs with empty input (defaults to a keyword search for `pressure sensors`).
- Enable a US-based proxy for the most reliable results.
- A keyword search typically yields around 25-30 suppliers; a letter page lists around 50 companies.
- Intended for research and lead-generation use; please respect GlobalSpec's terms of service.

# Actor input Schema

## `search_mode` (type: `string`):

'keyword' finds suppliers that match a product/keyword search (e.g. 'pressure sensors'). 'letter' browses the A-Z company directory page for one letter.

## `query` (type: `string`):

Product or keyword when search mode is 'keyword' (e.g. 'pressure sensors', 'hydraulic pumps'), or a single letter A-Z when it is 'letter' (use '1' for companies starting with a digit).

## `limit` (type: `integer`):

Maximum number of supplier records to return. A keyword search typically surfaces around 25-30 matching suppliers; a directory letter page lists around 50 companies.

## `fetch_profiles` (type: `boolean`):

Visit each supplier's profile page to add address, phone, fax, website, business type, logo and social links. Slower (one extra request per supplier) but much richer records.

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

Proxy settings for the run. Enable a US-based proxy for the most reliable results, especially for sites that limit non-US or datacenter traffic. Optional — leave off to run directly.

## Actor input object example

```json
{
  "search_mode": "keyword",
  "query": "pressure sensors",
  "limit": 25,
  "fetch_profiles": true,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# 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 = {
    "search_mode": "keyword",
    "query": "pressure sensors",
    "limit": 25,
    "fetch_profiles": true,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("moving_beacon-owner1/globalspec-supplier-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 = {
    "search_mode": "keyword",
    "query": "pressure sensors",
    "limit": 25,
    "fetch_profiles": True,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("moving_beacon-owner1/globalspec-supplier-scraper").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 '{
  "search_mode": "keyword",
  "query": "pressure sensors",
  "limit": 25,
  "fetch_profiles": true,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call moving_beacon-owner1/globalspec-supplier-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,moving_beacon-owner1/globalspec-supplier-scraper"
        }
    }
}

```

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/XLroYicpnVnCgb9RX/builds/ALLi2hLwceQeraUSO/openapi.json