we-online APIwe-online.com ↗
Search and retrieve electronic component specs, categories, and datasheets from Würth Elektronik's catalog via 4 structured REST endpoints.
What is the we-online API?
The we-online.com API provides 4 endpoints to query the Würth Elektronik electronic components catalog, returning product categories, series articles, and per-article electrical specifications with datasheet URLs. Use search_products to run full-text or order-code searches across the full catalog, or get_article_detail to fetch structured specs for a single SKU. Results include lifecycle status, spec key-value pairs, and direct links to PDF datasheets.
curl -X GET 'https://api.parse.bot/scraper/0b90659a-d40d-4059-b7e4-a3155c5c0482/search_products?query=inductor' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace we-online-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.wurth_elektronik_product_api import WurthElektronik, Product, Category, Article
client = WurthElektronik()
# Search for inductor products
for product in client.products.search(query="inductor"):
print(product.title, product.url, product.type)
# List all product categories
for category in client.categories.list():
print(category.name, category.id, category.url)
# Get all articles in a specific series
for article in client.articles.list_by_series(series_code="WE-MI"):
print(article.order_code, article.status, article.datasheet_url)
# Get detailed specs for a specific article
detail = client.articles.get(order_code="74479614")
print(detail.order_code, detail.status)
Full-text search across the Wurth Elektronik electronic components catalog. Matches product series and articles by keyword or order code. Returns a flat list of matching items with title, URL, and type classification. No pagination - server returns the top matches in one response.
| 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 API
Search and Category Navigation
search_products accepts a free-text keyword or a numeric order code (e.g. '74479614' or 'WE-MI') and returns a flat list of matching items, each with a title, url, and type field that classifies the result as a series or article. There is no pagination — the endpoint returns the top server-side matches in a single response. To browse without a search term, get_product_categories returns the full category tree with name, url, and id fields covering passive, active, electromechanical, optoelectronic, thermal, and automotive product groups.
Series and Article Data
get_series_articles accepts a series_code — either a named series like 'WE-MI' or a category path string from get_product_categories such as 'pbs/emc_components' — and returns every article (SKU) in that series. Each article object includes an order_code, a specs key-value map of electrical and physical parameters, a status string (e.g. 'Active'), and a datasheet_url pointing to the PDF. The total field in the response gives the article count for that series.
Single-Article Detail
get_article_detail takes a single order_code and returns the same structured shape: a specs object, status, and datasheet_url. The spec keys vary by component type — an inductor article will have different parameter names than a connector article. Order codes can be sourced from search_products or get_series_articles results, making the endpoints composable for catalog traversal workflows.
The we-online API is a managed, monitored endpoint for we-online.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when we-online.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official we-online.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Automated BOM validation: resolve order codes to lifecycle status and specs without manual catalog lookups
- Datasheet aggregation: collect datasheet_url fields across a product series for offline reference libraries
- Component cross-reference: search by series name or keyword to map Würth part numbers to electrical parameters
- Category-driven product discovery: enumerate all subcategories and series to build internal component databases
- Lifecycle monitoring: poll status fields for specific order codes to detect when parts move out of active status
- EDA tool enrichment: feed structured spec key-value pairs into schematic or simulation tools for Würth components
- Procurement filtering: retrieve all articles in a series and filter by spec values to shortlist candidate parts
| 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 | 100 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, and how do specs vary across component types?+
articles array where each item has an order_code, a specs object of key-value electrical and physical parameters, a status string, and a datasheet_url. The keys inside specs are not fixed — they reflect the attributes relevant to that component family, so an EMC component series will have different spec keys than a power inductor or connector series.Does search_products support pagination or filtering by category?+
search_products returns the top matches in a single response with no pagination or category filter parameter. For category-scoped browsing, use get_product_categories to get a category id or path, then pass that path to get_series_articles to enumerate articles within a specific product group.Does the API expose pricing or stock/availability data for articles?+
Can I retrieve parametric search results — for example, all inductors above a specific inductance value?+
get_series_articles, which returns structured specs key-value pairs, and then apply your own filtering logic client-side. You can also fork the API on Parse and revise it to add a parametric filter endpoint.