hondapartsnow.com APIhondapartsnow.com ↗
Access genuine Honda OEM parts data via 9 endpoints: browse by year/model/trim, look up parts by number or VIN, and retrieve pricing and fitment details.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/a70a9350-587a-4427-88e5-31beda9d0ff4/get_available_years' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns the list of all model years available on the site, from newest to oldest.
No input parameters required.
{
"type": "object",
"fields": {
"years": "array of integers representing available model years"
},
"sample": {
"data": {
"years": [
2026,
2025,
2024,
2023,
2022,
2021,
2020
]
},
"status": "success"
}
}About the hondapartsnow.com API
The HondaPartsNow API provides structured access to genuine Honda OEM parts data across 9 endpoints, covering everything from vehicle configuration to part-level pricing. Starting with get_available_years, you can walk the full vehicle hierarchy — year, model, trim, transmission — then pull parts catalogs, subcategory diagrams, and individual part specifications including MSRP, sale price, and fitment compatibility across Honda model years.
Vehicle Configuration Hierarchy
Browsing the parts catalog starts with vehicle selection. get_available_years returns an array of integers for all supported model years. Feed a year into get_models_by_year to get Honda model names, then pass year and model to get_trims_by_year_model to retrieve body and trim configurations. Finally, get_transmissions accepts trim, year, and model and returns available transmission strings (e.g. KA CVT, 6MT). These four endpoints together fully specify a vehicle before any parts lookup.
Parts Catalog and Detail
With a fully specified vehicle, get_vehicle_parts_categories returns top-level categories and their subcategories, each with a url_path for use in subsequent calls. Pass that path to get_parts_by_category along with the vehicle parameters to get a diagram image URL and a partList array where each entry includes name, image, url, and traffic fields. For individual parts, get_part_detail accepts an OEM part number (e.g. 04715-T0A-A90) and returns msrp, price, savings, a key-value attributes object for specifications, and a fitment_compatibility array listing every compatible vehicle by year, make/model, and body/trim.
Search and VIN Lookup
search_parts accepts a part number or keyword string. Part number queries return direct matches with url, name, price, msrp, and part_number fields, plus an exact_match boolean. Keyword searches return a message field and empty results, since keyword-based lookups require vehicle context that isn't available in a stateless query. lookup_by_vin decodes a 17-character VIN into currentYear, currentModel, currentMake, optionalInfo (body and trim), and requiredInfo, making it straightforward to resolve a VIN to a specific vehicle configuration before browsing parts.
- Build a Honda OEM parts finder that resolves user VINs to exact vehicle configs via
lookup_by_vinbefore showing parts - Aggregate current OEM pricing across part numbers using
get_part_detailMSRP and sale price fields - Generate fitment compatibility reports by extracting the
fitment_compatibilityarray from multiple part detail lookups - Populate a parts diagram viewer by combining category subcategory paths with the diagram URLs returned by
get_parts_by_category - Cross-reference OEM part numbers against aftermarket catalogs using the
part_numberandattributesfields fromget_part_detail - Automate inventory monitoring by periodically polling
search_partswith known part numbers and tracking price changes - Build a vehicle-to-parts hierarchy for a Honda repair app using the year → model → trim → transmission chain
| 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 HondaPartsNow have an official developer API?+
What does `get_part_detail` return beyond the price?+
get_part_detail returns msrp, price, savings (amount and percentage), a name string, an attributes object of key-value specification pairs, the part_number, and a fitment_compatibility array. Each fitment entry includes year, make_model, and body_trim, so you can see every Honda vehicle the part fits. If the part number is not found, the response includes a stale_input field with kind input_not_found.Does keyword search return part results?+
search_parts return a message field and an empty results array, because keyword-based browsing on hondapartsnow.com requires a vehicle to be selected first. Part number queries do return full results. You can fork this API on Parse and revise it to add a vehicle-scoped keyword search endpoint if that behavior is needed.Does the API cover Acura or other Honda-affiliated brands?+
lookup_by_vin returns currentMake as Honda, and get_models_by_year lists Honda model names. You can fork this API on Parse and revise it to point at an Acura-specific parts source if you need Acura data.Is there any pagination for `get_parts_by_category` or `search_parts` results?+
partList array from get_parts_by_category and the results array from search_parts return what is available for the given query in a single response. You can fork this API on Parse and revise it to add offset or page parameters if the source supports them.