we-online.com APIwe-online.com ↗
Search and retrieve electronic component specs, product categories, series articles, and datasheets from the Würth Elektronik catalog via 4 structured endpoints.
curl -X GET 'https://api.parse.bot/scraper/0b90659a-d40d-4059-b7e4-a3155c5c0482/search_products?query=capacitor' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for products by keyword or order code. Returns matching product series and articles from the Würth Elektronik catalog.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Search keyword or order code (e.g. 'inductor', '74479614', 'WE-MI') |
{
"type": "object",
"fields": {
"total": "integer count of results returned",
"results": "array of product objects with title, url, and type fields"
},
"sample": {
"data": {
"total": 15,
"results": [
{
"url": "https://www.we-online.com/en/components/products/category/1091207",
"type": "series",
"title": "Single Coil Power Inductors"
},
{
"url": "https://www.we-online.com/en/components/products/category/1382045",
"type": "series",
"title": "RF Inductors"
}
]
},
"status": "success"
}
}About the we-online.com API
The Würth Elektronik API exposes 4 endpoints to search, browse, and extract technical specifications from the we-online.com electronic components catalog. Use search_products to find matching series and articles by keyword or order code, get_series_articles to pull every SKU and its electrical parameters for a given series, and get_article_detail to retrieve lifecycle status and datasheet URLs for individual parts.
What the API covers
The API indexes Würth Elektronik's electronic components catalog — passive, active, electromechanical, optoelectronic, thermal, and automotive product groups. get_product_categories returns the full category tree with name, url, and id fields for each node, letting you map the hierarchy before drilling into specific product groups.
Searching and browsing products
search_products accepts a query string that can be a keyword (e.g. inductor), a series name (e.g. WE-MI), or a numeric order code (e.g. 74479614). The response includes a total count and a results array where each item carries title, url, and type — useful for distinguishing product series from individual articles in the same result set.
Series and article-level data
get_series_articles takes a series_code parameter, which can be a Würth series identifier like WE-PD or a catalog path like pbs/emc_components/filter_chokes. The response lists every article in that series with its order_code, a specs object containing electrical and physical parameters (values vary by product type), status, and datasheet_url. For a single part, get_article_detail accepts an order_code and returns the same shape: a specs object, status string (e.g. Active), and a direct URL to the PDF datasheet.
Spec fields and coverage notes
Spec keys in both get_series_articles and get_article_detail are product-type-dependent — an inductor returns inductance, DCR, and current rating fields, while a filter choke returns different parameters. The datasheet_url field points to Würth's own PDF hosting, so downstream workflows can fetch datasheets without additional lookup.
- Build a component search tool that surfaces Würth Elektronik series and articles matching a BOM keyword or part number.
- Automate BOM validation by checking
statusfields fromget_article_detailto flag obsolete or discontinued parts. - Populate a component database with full electrical specs by iterating
get_series_articlesacross catalog paths. - Generate parametric comparison tables for a product series using the
specsobjects returned per article. - Link directly to PDF datasheets in internal tooling using the
datasheet_urlfield without manual lookup. - Enumerate the full Würth Elektronik product hierarchy using
get_product_categoriesto seed a navigation interface. - Cross-reference order codes from a supplier quote against catalog specs and lifecycle status via
get_article_detail.
| 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 Würth Elektronik provide an official developer API?+
What does `get_series_articles` return compared to `get_article_detail`?+
get_series_articles returns all articles within an entire product series in one call — every order_code, specs object, status, and datasheet_url for that series. get_article_detail targets a single order_code and returns the same fields for that specific part. Use the series endpoint to bulk-extract a product line, and the detail endpoint when you already have a specific part number.Are pricing or availability data included in the article responses?+
Do spec field names stay consistent across different product types?+
specs object is keyed by parameter names that vary by component category — inductors, filter chokes, capacitors, and other product types each expose different fields. You should inspect the specs object dynamically rather than assuming fixed keys across product categories.Does the API cover Würth's connector or hardware product lines?+
get_product_categories returns the full catalog hierarchy including electromechanical categories, so connectors and hardware appear in the category tree. However, the depth of spec coverage for non-electronic components may vary. You can fork this API on Parse and revise it to add dedicated endpoints for connector or hardware series if the current coverage is insufficient for your use case.