RockAuto Parts Scraper avatar

RockAuto Parts Scraper

Pricing

from $1.60 / 1,000 rockauto parts scrapers

Go to Apify Store
RockAuto Parts Scraper

RockAuto Parts Scraper

Collect public RockAuto catalog part listings with brand, part number, listed price, currency, availability, and fitment notes. Run with catalog URLs; no RockAuto login. Pricing: $0.0016 per dataset item and $0.00005 per Actor start on the Free plan.

Pricing

from $1.60 / 1,000 rockauto parts scrapers

Rating

0.0

(0)

Developer

Vitalii Bondarev

Vitalii Bondarev

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

1

Monthly active users

a day ago

Last modified

Features

Limited permissions

Share

Scrape public RockAuto catalog pages for part brand, part number, listed price, currency, availability, and fitment notes. On the Free plan, billing is pay per event at $0.0016 per dataset item and $0.00005 per Actor start.

  • Compare listed prices, brands, and stock notes for one vehicle and part type, such as brake pads for a 2020 Toyota Camry.
  • Extract fitment notes, core prices, and part numbers when the catalog page includes them, for a purchase list or a catalog check.
  • Export make, year, model, engine, part category, and part type when those segments are present on the catalog URL.
  • No RockAuto login, cookie, or API key is requested; you only need your Apify account and catalog URLs.
  • Pass several catalog URLs in one run; the Actor caps rows at maxResults and skips a repeated part key on the same URL.

What you get

Each dataset item is one part listing. Page fields are written only when the parsed value is present and not blank. Make, year, model, engine, vehicle code, category, part type, and part type ID are read from the comma-separated /catalog/ path, not from a separate vehicle lookup. The dataset view is a table titled RockAuto part listings.

FieldTypeDetail
brandstringManufacturer text from the listing. Required for a row to be saved.
partNumberstringPart number from the listing. Required for a row to be saved.
pricenumberListed price parsed from the listing. Required for a row to be saved.
corePricenumberCore charge when a core price is parsed. A parsed zero is stored as 0. If none is parsed, the key is omitted.
currencystringCode from the price symbol shown on the page at collection time, so the same part can show a different currency than you expect: US$ and $ as USD, CA$ and C$ as CAD, AU$ and A$ as AUD, NZ$ as NZD, € as EUR, £ as GBP, ¥ as JPY, ₹ as INR. An unmapped symbol omits this key.
availabilitystringIn stock, Out of stock, or Non-stock item.
inStockbooleanFalse for out-of-stock and non-stock text. True when a price was parsed and neither phrase is present.
descriptionstringExtra listing description when that text is present.
fitmentNotesstringListing text kept as fitment notes, including position or closeout wording when the page shows it.
partKeystringpk value from the part information link, when that link exists.
infoUrlstringAbsolute moreinfo.php URL when the listing has an information link.
catalogUrlstringCatalog URL that produced the row.
makestringMake from the catalog URL, uppercased.
yearintegerModel year from the catalog URL when that segment is numeric.
modelstringModel from the catalog URL, uppercased.
enginestringEngine from the catalog URL, uppercased.
carcodeintegerRockAuto vehicle code from the catalog URL when that segment is numeric.
partCategorystringCategory from the catalog URL, in title case.
partTypestringPart type from the catalog URL, in title case.
partTypeIdintegerPart type ID from the catalog URL when that segment is numeric.

Sample output

One record from a successful run is below. The sample is shortened by dropping partKey, infoUrl, carcode, and partTypeId. Every remaining value is unchanged.

Note: Prices, currency, and availability reflect the catalog page at collection time. The currency code comes from the symbol the page showed then, which is why this US Camry sample shows GBP.

{
"brand": "PRO LINE",
"partNumber": "PS1212C",
"price": 7.26,
"corePrice": 0,
"currency": "GBP",
"availability": "In stock",
"inStock": true,
"description": "Includes Pad Installation Hardware",
"fitmentNotes": "Rear; Ceramic [ Wholesaler Closeout -- 30 Day Warranty ]",
"make": "TOYOTA",
"year": 2020,
"model": "CAMRY",
"engine": "2.5L L4",
"partCategory": "Brake & Wheel Hub",
"partType": "Brake Pad",
"catalogUrl": "https://www.rockauto.com/en/catalog/toyota,2020,camry,2.5l+l4,3445372,brake+%26+wheel+hub,brake+pad,1684"
}

Pricing

This Actor uses pay-per-event billing. Prices below are Free-plan prices.

EventFree-plan priceWhen it is charged
Actor start (apify-actor-start)$0.00005 per eventCharged when the Actor starts. The number of events depends on memory: one event per GB, with a minimum of one event.
RockAuto Parts Scraper (apify-default-dataset-item)$0.0016 per dataset itemOne scraped result with all fields written to the default dataset. This is the primary event.

50 results = $0.08005 on Free, from 50 × $0.0016 plus one Actor start at $0.00005.

1,000 results = $1.6 on Free, from 1,000 × $0.0016.

10,000 results = $16 on Free, from 10,000 × $0.0016.

The Apify Free plan includes $5 of monthly platform usage credit. After one Actor start, that credit covers 3124 dataset items: 3124 × $0.0016 on Free is $4.9984, and one start adds $0.00005, for $4.99845.

The default memory is 512 MB, which charges one start event. A higher memory setting charges more than one start event and leaves less of the Free-plan $5 credit for items.

Note: On this pay-per-event Actor, platform usage (compute, Apify Proxy traffic including residential, and storage) is included in the event prices and paid by the Actor developer.

How to use

  1. Open RockAuto Parts Scraper in your Apify account.
  2. Paste one or more HTTPS RockAuto catalog URLs into startUrls. After /catalog/, the comma-separated segments are make, year, model, engine, vehicle code, category, part type, and part type ID.
  3. Set maxResults, the total number of records pushed across all URLs; the default is 50.
  4. Keep the proxy configuration, or set useApifyProxy to false to connect directly to RockAuto.
  5. Start the run and open the default dataset.
  6. Schedule a repeat run in Apify Schedules. Daily is a starting point for listed prices and availability, not a statement of how often RockAuto updates pages.
{
"startUrls": [
"https://www.rockauto.com/en/catalog/toyota,2020,camry,2.5l+l4,3445372,brake+%26+wheel+hub,brake+pad,1684"
],
"maxResults": 50,
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": ["RESIDENTIAL"]
}
}

Export the default dataset as JSON or CSV, or read it through the Apify dataset API.

Input parameters

ParameterWhat it doesDefault
startUrlsRequired list of catalog URLs. A single string counts as one URL; non-string entries are ignored. With no URL left, the built-in Camry brake-pad URL is used. See Limits for URL validation.Required. Prefill and code fallback: the Camry brake-pad catalog URL in the example above.
maxResultsMaximum part records pushed across all URLs. A value that cannot be converted to an integer falls back to 50. The schema accepts only integers from 1 to 1000000; the run clamps anything else into 0 to 1000000. Zero ends the run before any request.50 (schema minimum 1, schema maximum 1000000)
proxyConfigurationApplied only when the object is present and useApifyProxy is true; otherwise requests connect directly to RockAuto.useApifyProxy true and apifyProxyGroups RESIDENTIAL

Limits and edge cases

ConditionWhat you seeWhat to do
maxResults is 0 or negativeThe run ends with no RockAuto request and no dataset items.Set maxResults to at least 1.
More listings than maxResultsPushing stops at the cap. Once enough listings are parsed, the rest of that catalog page is not downloaded. The log reports how many listings were parsed on each URL that was fetched, which can be higher than the number pushed. URLs after the cap is reached are not fetched.Raise maxResults. Values above 1000000 are clamped to 1000000.
Same part repeated on one catalog URLA later row with the same partKey, or the same partNumber when partKey is missing, is not pushed. The same part on a different catalog URL is kept.Nothing to change. Duplicates are only detected within the current run.
Brand, part number, or price missingThat listing is skipped. A succeeded run can finish with an empty dataset if every card is skipped.Use a catalog URL that shows priced, identified parts.
Blank optional textKeys such as description, fitmentNotes, corePrice, infoUrl, partKey, or currency are absent. A missing corePrice is not the same as a stored 0.Read the keys that exist on each item.
URL fails the catalog checkThe run fails before any request with Each startUrls entry must be an HTTPS RockAuto catalog URL. Nothing is pushed.Replace the input with an https rockauto.com link whose path contains /catalog/.
Challenge page and zero parsed listingsThe page is requested again through a new proxy session, up to 3 attempts. If every attempt is challenged, that URL is skipped and the log names it; when no URL delivered any item, the run fails with RockAuto returned a challenge page instead of catalog listings.Start a new run, keeping the default RESIDENTIAL proxy configuration. A proxy does not guarantee the page loads.
HTTP error or 45-second timeoutThe request is retried through a new proxy session, up to 3 attempts. HTTP 400, 401, 404, 405, 410, 414 and 451 are not retried. A URL that still fails is skipped; the run fails only when no URL delivered any item, and otherwise finishes with a status message counting the failed URLs.Check the catalog URL and proxy setting, then start a new run.

Only one catalog page is fetched per URL. Listings that are not in that page’s HTML are not collected.

FAQ

How much does it cost to scrape RockAuto?

Unit prices, the 50-result example, and the Free-plan $5 credit are in Pricing.

Why is the dataset empty?

maxResults is 0, every listing lacked a brand, part number, or parseable price, or the page HTML had no listings.

Why did the run fail?

Invalid URLs fail the run before any request. Challenge pages, HTTP errors, and 45-second timeouts are retried up to 3 times through new proxy sessions; the run fails only when no catalog URL delivered any item. Rows already pushed stay. Each case and the fix are in Limits and edge cases.

Which RockAuto URLs work?

HTTPS on rockauto.com or a subdomain, with /catalog/ in the path. Other links fail validation. Paste the catalog link from the browser.

Is collecting public RockAuto data allowed?

The Actor reads publicly accessible RockAuto catalog pages that you supply. Whether that use is allowed depends on RockAuto’s terms and on the law that applies to your use case. This README does not say that a public page makes every use lawful, and it is not a legal guarantee.