# AllDataSheet Electronic Component Datasheet Scraper (`jungle_synthesizer/alldatasheet-electronic-component-pdf-scraper`) Actor

Search AllDataSheet.com by part number, category, or keyword. Get manufacturer, part number, description, page count, revision date, and a direct link. Optionally extract the full datasheet text and a RoHS-compliance signal. Built for EE design, BOM cost-down, and sourcing teams.

- **URL**: https://apify.com/jungle\_synthesizer/alldatasheet-electronic-component-pdf-scraper.md
- **Developed by:** [BowTiedRaccoon](https://apify.com/jungle_synthesizer) (community)
- **Categories:** E-commerce, Developer tools, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.00 / 1,000 record scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## AllDataSheet Electronic Component Datasheet Scraper

Search [AllDataSheet.com](https://www.alldatasheet.com) by part number, keyword, or category and get structured component data back: manufacturer, part number, description, datasheet page count, revision date, and a direct datasheet link. Optionally extract the **full datasheet text** — the actual PDF contents, parsed — for BOM cost-down, part qualification, and component-search tooling.

***

### AllDataSheet Electronic Component Datasheet Scraper Features

- Searches by **part number**, **keyword**, or **category** — one input covers all three
- Returns a normalized `mpn_normalized` alongside the raw part number, so results join cleanly against your own BOM
- Extracts the **full datasheet text** on request (`includeFullText`), not just metadata — the PDF is fetched and parsed, not linked and forgotten
- Reports the real `pdf_page_count` and `datasheet_revision_date` straight from the document
- Filters by manufacturer when a part number is carried by several vendors
- Fails loudly when the source blocks a request instead of quietly reporting "no results"

***

### Who Uses AllDataSheet Data?

- **Electronics design engineers** — pull datasheet text into part-selection and comparison tooling
- **Sourcing and procurement teams** — resolve manufacturer and MPN variants across a BOM
- **BOM cost-down analysts** — find alternate parts by category and specification text
- **Component distributors** — enrich catalog listings with manufacturer descriptions and revision dates
- **Engineering-search products** — index datasheet contents for full-text component search

***

### How AllDataSheet Electronic Component Datasheet Scraper Works

1. Choose a `mode` — `by_part_number` (or keyword) to search the part index, or `by_category` to browse a named category.
2. Supply `partNumbers` or `categories` accordingly, and optionally a `manufacturers` filter.
3. The scraper resolves each match to its datasheet page and reads the document metadata.
4. With `includeFullText: true`, the datasheet PDF is downloaded and its text extracted into `full_pdf_text`.
5. Records land in your dataset as they're scraped, up to your `maxItems` cap.

***

### Input

```json
{
  "mode": "by_part_number",
  "partNumbers": ["STM32F407VG", "LM358", "ATMEGA328P"],
  "includeFullText": false,
  "maxItems": 10
}
```

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `mode` | string | `by_part_number` | `by_part_number` / `by_keyword` search the part-number index; `by_category` browses a named category |
| `partNumbers` | array | — | Part numbers or keywords to search (used by `by_part_number` / `by_keyword`) |
| `categories` | array | — | Category names to browse (used by `by_category`) |
| `manufacturers` | array | — | Optional manufacturer filter, for parts carried by multiple vendors |
| `includeFullText` | boolean | `false` | Download each datasheet PDF and extract its full text into `full_pdf_text` |
| `maxItems` | integer | 10 | Maximum number of records to scrape (required) |

Browse a category instead of searching part numbers:

```json
{
  "mode": "by_category",
  "categories": ["LED"],
  "maxItems": 50
}
```

***

### AllDataSheet Electronic Component Datasheet Scraper Output Fields

```json
{
  "manufacturer": "STMicroelectronics",
  "part_number": "STM32F407VG",
  "mpn_normalized": "STM32F407VG",
  "category": "",
  "description": "ARM Cortex-M4 32b MCU+FPU, 210DMIPS, up to 1MB Flash/192+4KB RAM, USB OTG HS/FS, Ethernet, 17 TIMs, 3 ADCs, 15 comm. interfaces & camera",
  "pdf_url": "https://www.alldatasheet.com/datasheet-pdf/pdf/504999/STMICROELECTRONICS/STM32F407VG.html",
  "pdf_page_count": 167,
  "datasheet_revision_date": "24-Jan-2012",
  "rohs_compliant": null,
  "full_pdf_text": ""
}
```

| Field | Type | Notes |
|-------|------|-------|
| `manufacturer` | string | Manufacturer as listed by the source |
| `part_number` | string | Part number as listed |
| `mpn_normalized` | string | Normalized MPN for joining against your own data |
| `category` | string | Category, when the source supplies one for the match |
| `description` | string | Manufacturer's own one-line part description |
| `pdf_url` | string | Direct link to the datasheet document page |
| `pdf_page_count` | number | Real page count, read from the parsed PDF |
| `datasheet_revision_date` | string | Revision date printed on the datasheet |
| `rohs_compliant` | boolean | null | `true` only when the datasheet states RoHS compliance explicitly; `null` when it doesn't say. Never guesses `false` |
| `full_pdf_text` | string | Full extracted datasheet text — populated only when `includeFullText: true` |

#### Why some fields are null

`full_pdf_text` is empty unless you set `includeFullText: true` — extracting a multi-hundred-page PDF is opt-in, not the default.

`rohs_compliant` is deliberately **asymmetric**: it reports `true` where a datasheet states compliance and `null` where the document is silent. It never reports `false`, because "the datasheet doesn't mention RoHS" is not evidence that a part is non-compliant. Measured fill rate across sampled parts: 1/10.

Fields covering package type, pin count, operating temperature range, supply voltage range, lifecycle status, pin-outs and electrical-characteristics tables were **deliberately not shipped**. AllDataSheet serves family datasheets that cover many variants at once, and every one of those values was verified to return the wrong variant's figure on multi-part documents. Wrong specifications are worse than absent ones in a sourcing workflow.

***

### Frequently Asked Questions

**Does it extract the actual datasheet contents, or just links?**
Actual contents. Set `includeFullText: true` and the PDF is downloaded and parsed into `full_pdf_text`.

**Why is `category` sometimes empty?**
Part-number searches don't always carry a category on the result row; category browsing always does.

**What happens if the source blocks the request?**
The run fails with an explicit block error. It will not exit successfully with zero rows and tell you to widen your filters.

**Can I search several parts in one run?**
Yes — `partNumbers` takes an array, and `maxItems` caps the total records returned.

# Actor input Schema

## `sp_intended_usage` (type: `string`):

What will this data feed? E.g. lead lists, KYB checks, price tracking.

## `sp_improvement_suggestions` (type: `string`):

Provide any feedback or suggestions for improvements.

## `sp_contact` (type: `string`):

We'll personally help with your use case. No spam.

## `mode` (type: `string`):

How to search AllDataSheet.com. by\_part\_number/by\_keyword both search the part-number index (partNumbers); by\_category browses a named category (categories).

## `partNumbers` (type: `array`):

Part numbers (or keyword prefixes) to search for. Used by by\_part\_number and by\_keyword modes.

## `categories` (type: `array`):

Category names to browse (e.g. LED, MOSFET, MCU) — used by by\_category mode. AllDataSheet's category taxonomy is loaded client-side and isn't statically enumerable, so this is free text passed directly as the site's own category search term.

## `manufacturers` (type: `array`):

Optional: keep only results whose manufacturer name contains one of these (case-insensitive). Applies to every mode. AllDataSheet's manufacturer/distributor catalogue-browse endpoints are robots.txt-disallowed sitewide, so this is a post-filter on search results rather than a full-catalogue browse.

## `includeFullText` (type: `boolean`):

When true, downloads and extracts the full datasheet PDF (all pages) to fill full\_pdf\_text and rohs\_compliant. Off by default — slower, and OCR-billed on the (uncommon) scanned/older documents that need it.

## `maxItems` (type: `integer`):

Maximum number of datasheet records to return, across all search terms combined.

## Actor input object example

```json
{
  "sp_intended_usage": "Describe your intended use...",
  "sp_improvement_suggestions": "Share your suggestions here...",
  "sp_contact": "Share your email here...",
  "mode": "by_part_number",
  "partNumbers": [
    "STM32F407VG",
    "LM358",
    "ATMEGA328P"
  ],
  "categories": [
    "LED"
  ],
  "manufacturers": [],
  "maxItems": 10
}
```

# 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 = {
    "sp_intended_usage": "Describe your intended use...",
    "sp_improvement_suggestions": "Share your suggestions here...",
    "sp_contact": "Share your email here...",
    "mode": "by_part_number",
    "partNumbers": [
        "STM32F407VG",
        "LM358",
        "ATMEGA328P"
    ],
    "categories": [
        "LED"
    ],
    "manufacturers": [],
    "includeFullText": false,
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("jungle_synthesizer/alldatasheet-electronic-component-pdf-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 = {
    "sp_intended_usage": "Describe your intended use...",
    "sp_improvement_suggestions": "Share your suggestions here...",
    "sp_contact": "Share your email here...",
    "mode": "by_part_number",
    "partNumbers": [
        "STM32F407VG",
        "LM358",
        "ATMEGA328P",
    ],
    "categories": ["LED"],
    "manufacturers": [],
    "includeFullText": False,
    "maxItems": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("jungle_synthesizer/alldatasheet-electronic-component-pdf-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 '{
  "sp_intended_usage": "Describe your intended use...",
  "sp_improvement_suggestions": "Share your suggestions here...",
  "sp_contact": "Share your email here...",
  "mode": "by_part_number",
  "partNumbers": [
    "STM32F407VG",
    "LM358",
    "ATMEGA328P"
  ],
  "categories": [
    "LED"
  ],
  "manufacturers": [],
  "includeFullText": false,
  "maxItems": 10
}' |
apify call jungle_synthesizer/alldatasheet-electronic-component-pdf-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jungle_synthesizer/alldatasheet-electronic-component-pdf-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/iAbJZK1KO9ceP7RIu/builds/BPFq5sDNeTcXn3WPr/openapi.json