datasheetcatalog.com APIdatasheetcatalog.com ↗
Search electronic component datasheets, retrieve PDF links, and browse by manufacturer or category using the DatasheetCatalog.com API. 6 endpoints.
curl -X GET 'https://api.parse.bot/scraper/6287ee91-bb37-4c16-9240-16ab0dfe8072/search_datasheets' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for datasheets by part name, description, or keyword. Returns list of matching components.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination |
| queryrequired | string | Search keyword or part number |
{
"type": "object",
"fields": {
"page": "integer",
"query": "string",
"results": "array of objects (part_name, description, manufacturer, detail_url)"
},
"sample": {
"page": 1,
"query": "NE555",
"results": [
{
"part_name": "NE555",
"detail_url": "http://www.datasheetcatalog.com/datasheets_pdf/N/E/5/5/NE555.shtml",
"description": "General Purpose Timer",
"manufacturer": "Texas Instruments"
}
]
}
}About the datasheetcatalog.com API
The DatasheetCatalog API provides 6 endpoints for finding electronic component datasheets, retrieving direct PDF download links, and browsing the full catalog by manufacturer or component category. The search_datasheets endpoint accepts part numbers or keywords and returns matching components with manufacturer attribution, while get_datasheet_detail exposes all available PDF variants for a given component, including per-manufacturer pdf_url fields.
Search and Component Detail
The search_datasheets endpoint accepts a query string (part number, keyword, or description fragment) and an optional page integer for pagination. Each result in the results array includes part_name, description, manufacturer, and a detail_url that can be passed directly to get_datasheet_detail. That detail endpoint returns a manufacturers array where each entry carries its own pdf_url (a direct link to the datasheet PDF), a pdf_page_url, and a description — useful when the same part is manufactured by multiple vendors with differing specs. It also returns a related_parts array of similar components with their own detail_url values.
Browsing by Manufacturer
get_manufacturer_list returns the full catalog of indexed manufacturers as an array of objects with name, slug, and url. Pass a manufacturer_slug from that list to get_manufacturer_components to retrieve all datasheets attributed to that manufacturer, paginated via the page parameter. Each component in the response carries part_name, description, and detail_url.
Browsing by Category
get_category_list returns the hierarchical list of component function categories — each with name, slug, and url. Pass a category_slug to get_category_components to get all components in that category, with each entry including part_name, description, manufacturer, and detail_url. Together the category and manufacturer endpoints make it possible to enumerate the catalog without an upfront search query.
- Resolve a part number to a direct PDF datasheet link using
search_datasheetsthenget_datasheet_detail. - Compare PDF datasheets from multiple manufacturers for the same component using the
manufacturersarray inget_datasheet_detail. - Build a component browser that enumerates all parts from a given supplier via
get_manufacturer_components. - Classify components by function by iterating category slugs from
get_category_listand fetching parts viaget_category_components. - Populate a parts database with manufacturer metadata by combining
get_manufacturer_listwith paginatedget_manufacturer_componentscalls. - Surface related components for a BOM alternative-search tool using the
related_partsfield fromget_datasheet_detail. - Index component descriptions and part names for full-text search by paginating through manufacturer or category component listings.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does DatasheetCatalog.com offer an official developer API?+
What does `get_datasheet_detail` return beyond a single PDF link?+
manufacturers array, so if a part is sourced from several manufacturers you get a separate pdf_url, pdf_page_url, manufacturer, and description entry for each one. It also returns a related_parts array listing similar components with their own detail_url values for further lookup.Does `search_datasheets` support filtering by manufacturer or category directly?+
search_datasheets endpoint accepts only a query string and an optional page for pagination — there is no manufacturer or category filter parameter on the search endpoint itself. Manufacturer- and category-scoped browsing is handled by the dedicated get_manufacturer_components and get_category_components endpoints. You can fork the API on Parse and revise it to add filtered search parameters to the search endpoint.Does `get_category_components` support pagination?+
get_category_components endpoint does not expose a page parameter — it returns results for a category slug without pagination controls, unlike get_manufacturer_components which does support page. For large categories this may limit the result set. You can fork the API on Parse and revise it to add pagination support to the category components endpoint.Does the API expose component specifications like voltage, package type, or pin count from within the datasheet?+
part_name, description, manufacturer, and pdf_url — rather than parsed electrical or physical specifications extracted from the datasheet content. You can fork the API on Parse and revise it to add a spec-extraction endpoint targeting specific component parameters.