arrow.com APIarrow.com ↗
Search Arrow.com's catalog via API. Get part pricing, availability, specs, RoHS compliance, and manufacturer listings for electronic components.
curl -X GET 'https://api.parse.bot/scraper/552c786b-18f1-4a60-ad01-97304694eebe/search_by_token?rows=25&start=0&search_token=NE555' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for electronic components by part number or keyword. Returns matching products with manufacturer info, descriptions, pricing tiers, availability, compliance data, and category taxonomy from Arrow.com's search API.
| Param | Type | Description |
|---|---|---|
| rows | integer | Number of results per page. |
| start | integer | Result offset for pagination (0-based). Page is calculated as start/rows + 1. |
| search_tokenrequired | string | Part number or keyword to search for (e.g. 'NE555', 'LM358', 'Arduino'). |
{
"type": "object",
"fields": {
"facets": "array of filter facets (product line, manufacturer, status)",
"products": "array of product objects with pricing, availability, manufacturer info",
"taxonomy": "array of category hierarchy objects",
"pagination": "object with currentPage, pageSize, totalPages, totalResults",
"resultCount": "string total number of matching products",
"searchKeyword": "array of search terms used"
},
"sample": {
"data": {
"facets": [
{
"code": "manufacturername",
"name": "Manufacturer_name",
"values": [
{
"count": 23,
"value": "Texas Instruments"
}
]
}
],
"products": [
{
"euRohs": "Compliant",
"mfrName": "Texas Instruments",
"fullPart": "NE555P",
"partStatus": "Active",
"groupByPrice": {
"hasPrice": true,
"totalStock": 2200
},
"calculatedPrice": "0.26520852",
"productLineName": "Timers",
"calculatedQuantity": "700",
"storedPartDescription": "Standard Timer Single 0°C 70°C 8-Pin PDIP Tube"
}
],
"taxonomy": [
{
"categories": [
{
"name": "Clock and Timing",
"productCount": 27
}
],
"productLineType": "Semiconductor"
}
],
"pagination": {
"pageSize": 25,
"totalPages": 2,
"currentPage": 1,
"totalResults": 27
},
"resultCount": "27",
"searchKeyword": [
"ne555"
]
},
"status": "success"
}
}About the arrow.com API
The Arrow.com API exposes 4 endpoints for querying Arrow Electronics' electronic components catalog, covering part search, batch lookups, product details, and manufacturer listings. The search_by_token endpoint returns pricing tiers, stock availability, compliance data, and category taxonomy for any part number or keyword. The get_product_detail endpoint returns 10+ structured fields per component including ECCN export codes, RoHS status, and total stock across regions.
Search and Batch Lookup
The search_by_token endpoint accepts a search_token (part number or keyword such as NE555 or Arduino) and returns a products array with manufacturer info, pricing tiers, stock availability, and facets for filtering by product line, manufacturer, and status. Pagination is controlled via rows (results per page) and start (zero-based offset); the response includes a pagination object with currentPage, totalPages, and totalResults. A taxonomy array provides the full category hierarchy for each result set.
For bulk workflows, search_by_list accepts a JSON array of part numbers via the parts_json parameter — either plain strings like ["LM358", "NE555"] or objects with a partNum key. It runs each query sequentially and returns an aggregated response with results (per-query results arrays), errors (failed queries with error messages), total_queries, and successful_queries. This is practical for BOM (bill of materials) validation where you need to check dozens of parts at once.
Product Details and Manufacturers
The get_product_detail endpoint takes a part_url in the format /en/products/<part-number-slug>/<manufacturer-slug> and returns a fully structured record: sku, partNumber, name, partStatus (Active, Obsolete, or NRND), totalStock, price (lowest USD price), euRohs compliance status, eccnCode for export control, category, and a product image URL. This is the endpoint to use when you already know the exact part and manufacturer.
The lookup_manufacturer endpoint requires no inputs and returns the complete list of manufacturers on Arrow.com — over 1,000 — with each entry's manufacturerName and productCount. This is useful for enumerating suppliers or building manufacturer-filtered search flows.
- BOM validation: batch-check a list of part numbers against live Arrow stock and pricing using
search_by_list - Component sourcing dashboards that display real-time
totalStockandpricefor a shortlist of parts - Compliance screening: filter components by
euRohsstatus andeccnCodebefore procurement - Obsolescence tracking: monitor
partStatus(Active, Obsolete, NRND) across a component library - Manufacturer discovery: enumerate all Arrow-stocked suppliers and their product counts via
lookup_manufacturer - Alternative part research: use keyword search via
search_by_tokento find substitute components by function or category - Catalog enrichment: pull structured specs and images via
get_product_detailto populate an internal parts database
| 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 Arrow Electronics have an official developer API?+
What does `get_product_detail` return beyond basic pricing?+
euRohs compliance status, eccnCode for export control classification, partStatus (Active, Obsolete, or NRND), totalStock across all regions, a product image URL, sku, and the category (product line name) — all in a single call given a valid part_url path.Does `search_by_token` support filtering results by manufacturer or status?+
facets array that includes manufacturer, product line, and status breakdowns for the result set, but the endpoint parameters don't currently accept facet filters as inputs — the filtering must be applied client-side. You can fork this API on Parse and revise it to pass facet filter parameters through to narrow results server-side.Does the API return historical pricing or price change data?+
get_product_detail. Historical price tracking is not covered. You can fork this API on Parse and revise it to add a scheduled polling endpoint that stores price snapshots over time.How does pagination work in `search_by_token`?+
start offset (zero-based) and a rows count. The response pagination object returns currentPage (calculated as start / rows + 1), pageSize, totalPages, and totalResults. To iterate through all results, increment start by rows on each request until currentPage equals totalPages.