MyMoparParts APImymoparparts.com ↗
Search and retrieve genuine Mopar OEM part listings, pricing, fitment, and superseded part numbers from MyMoparParts.com via a simple REST API.
What is the MyMoparParts API?
The MyMoparParts API provides two endpoints for accessing genuine Mopar OEM parts data, returning over 10 structured fields per product including sale price, MSRP, savings, and vehicle fitment. The search_parts endpoint accepts part name keywords, OEM part numbers, or a VIN to return paginated catalog results across the full MyMoparParts inventory, while get_product_details delivers complete part records including hazmat status, superseded part numbers, and multiple product images.
curl -X GET 'https://api.parse.bot/scraper/0eaf64e3-b145-4697-bb6b-9dcc41fbeada/search_parts?page=1&query=brake+pad' \ -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 mymoparparts-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.
"""Walkthrough: MyMoparParts SDK — search parts and get pricing details."""
from parse_apis.mymoparparts_com_api import MyMoparParts, PartNotFound
client = MyMoparParts()
# Search for brake pads — limit caps total items fetched across all pages.
for part in client.parts.search(query="brake pad", limit=5):
print(part.name, part.part_number, part.sale_price, part.msrp)
# Drill into the first result for full pricing and product details.
first = client.parts.search(query="oil filter", limit=1).first()
if first:
try:
detail = first.details()
print(detail.name, detail.sku, detail.price, detail.msrp, detail.currency)
print("Replaces:", detail.replaces)
print("Hazmat:", detail.hazmat_info)
except PartNotFound as exc:
print(f"Product gone: {exc}")
print("exercised: parts.search / PartSummary.details")
Full-text search across the MyMoparParts catalog by keyword, part number, or VIN. Returns paginated product listings with pricing, brand, and availability. Results are auto-iterated across pages.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for results pagination. |
| queryrequired | string | Search term: part name keyword, OEM part number, or VIN. |
{
"type": "object",
"fields": {
"page": "integer",
"query": "string",
"products": "array of product summaries with name, brand, part_number, sale_price, msrp, savings, savings_percent, description, url, image_url, availability",
"total_pages": "integer",
"total_results": "integer"
},
"sample": {
"data": {
"page": 1,
"query": "brake pad",
"products": [
{
"url": "https://www.mymoparparts.com/oem-parts/mopar-brake-pads-68334863aa",
"msrp": "139.00",
"name": "Brake Pads",
"brand": "Mopar",
"savings": "40.24",
"image_url": "https://cdn-product-images.revolutionparts.io/assets/17aac4ce6844bb7d2b74d45fe4c1f59f.webp",
"sale_price": "98.76",
"description": "Vehicles built 9/11/09 and after. V-Line Kits Do Not Include Clips.",
"part_number": "68334863AA",
"savings_percent": "28.9% Off"
}
],
"total_pages": 6,
"total_results": 823
},
"status": "success"
}
}About the MyMoparParts API
Search the Mopar Catalog
The search_parts endpoint accepts a query parameter that can be a plain-language keyword (e.g. "brake pads"), a specific OEM part number, or a VIN. Results are paginated and include total_results and total_pages counts alongside an array of product summaries. Each product summary carries name, brand, part_number, sale_price, msrp, savings, savings_percent, description, url, and image_url. An optional page parameter navigates through multi-page result sets.
Product Detail Records
The get_product_details endpoint accepts a product_path — either a full URL or a relative path such as oem-parts/mopar-brake-pads-68334863aa — obtained from a prior search_parts response. It returns a complete record with mpn, sku, price, msrp, brand, name, currency, an images array, and a replaces array listing any superseded OEM part numbers. The replaces field is particularly useful when a part has been updated and older part numbers still appear in service manuals.
Fitment and Hazmat Data
Beyond pricing, get_product_details surfaces vehicle fitment data so you can verify a part applies to the intended year/make/model/trim combination. Hazmat status is also returned, which matters for shipping calculations on parts like batteries or aerosol products. These fields are not available in the lighter summary objects returned by search_parts, making the two-endpoint flow the standard pattern for full data retrieval.
The MyMoparParts API is a managed, monitored endpoint for mymoparparts.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when mymoparparts.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 mymoparparts.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?+
- Look up current sale price and MSRP for a Mopar part by OEM part number to compare against third-party supplier pricing.
- Search by VIN to surface catalog results relevant to a specific vehicle, then retrieve fitment details per part.
- Build a superseded-part resolver that maps legacy OEM part numbers to current replacements using the
replacesfield. - Aggregate savings and savings_percent data across search results to identify the highest-discounted Mopar parts.
- Flag hazmat parts during checkout flows to apply correct shipping rules before a customer completes an order.
- Populate an internal parts database with structured name, brand, MPN, SKU, and image URLs for Mopar inventory.
| 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 MyMoparParts.com have an official developer API?+
What does search_parts return when I query by VIN versus a part number?+
query parameter and return the same product summary structure — name, brand, part_number, sale_price, msrp, savings, savings_percent, description, url, and image_url. The VIN path filters results to parts cataloged for that specific vehicle, while a part number query targets a specific SKU. Pagination fields (total_results, total_pages, page) are present in both cases.Does the API return customer reviews or seller ratings for parts?+
Can I retrieve a full compatibility list — all vehicles a part fits — from get_product_details?+
get_product_details endpoint returns vehicle fitment data, but the depth of that fitment list (e.g. whether it enumerates every compatible year/make/model/trim) is bounded by what appears on the product page. If you need a structured multi-vehicle fitment table not currently surfaced in the response fields, you can fork the API on Parse and revise it to capture that data.How are superseded part numbers handled?+
get_product_details response includes a replaces array listing OEM part numbers that the current part supersedes. This covers cases where Mopar has updated a component and retired older numbers. The search_parts endpoint does not include this array — it appears only in the full detail record.