Discover/Row52 API
live

Row52 APIrow52.com

Access Row52 junkyard vehicle inventory by location. Returns VIN, make, model, year, row number, and date added for every vehicle at a yard.

Endpoint health
verified 5d ago
get_yard_vehicles
1/1 passing latest checkself-healing
Endpoints
1
Updated
25d ago

What is the Row52 API?

The Row52 API exposes vehicle inventory data from self-service recycling yards across the Row52 network. A single endpoint, get_yard_vehicles, returns up to 8 fields per vehicle — including VIN, row number, and date added — across all paginated results for a given yard location. Whether you're hunting a specific donor car or building a parts-sourcing tool, the API delivers the same inventory data visible on the Row52 search page.

Try it
Maximum number of pages to fetch (30 vehicles per page).
The yard location ID (e.g., '88' for PICK-n-PULL Windsor, '89' for PICK-n-PULL Carson City).
api.parse.bot/scraper/6aff89ac-9cc7-414c-b0f9-9524d9cabdf3/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/6aff89ac-9cc7-414c-b0f9-9524d9cabdf3/get_yard_vehicles?max_pages=1&location_id=88&max_age_days=3' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

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 row52-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.

"""Row52 yard vehicle search — browse recycling yard inventory."""
from parse_apis.row52_yard_vehicle_search_api import Row52, Vehicle, YardNotFound

client = Row52()

# Construct a yard by location_id and list its vehicles (capped).
yard = client.yard(location_id="88")
for vehicle in yard.vehicles(max_pages=1, limit=5):
    print(vehicle.year, vehicle.make, vehicle.model, vehicle.vin)

# Get yard metadata via the collection accessor.
windsor = client.yards.get(location_id="88")
print(windsor.name, windsor.total_results, "vehicles across", windsor.total_pages, "pages")

# Drill into first vehicle from another yard.
first = client.yard(location_id="89").vehicles(max_pages=1, limit=1).first()
if first:
    print(first.year, first.make, first.model, "row:", first.row_number, "added:", first.date_added)

# Typed error handling for a nonexistent yard.
try:
    client.yards.get(location_id="99999")
except YardNotFound as exc:
    print(f"Yard not found: location_id={exc.location_id}")

print("exercised: yard.vehicles / yards.get / YardNotFound error")
All endpoints · 1 totalmissing one? ·

Get all vehicles at a specific yard location, paginated. Returns vehicle details from the first N pages of results (30 vehicles per page). Each page contains up to 30 vehicles. The response includes yard metadata (name, total results, total pages) alongside the vehicle array.

Input
ParamTypeDescription
max_pagesintegerMaximum number of pages to fetch (30 vehicles per page).
location_idrequiredstringThe yard location ID (e.g., '88' for PICK-n-PULL Windsor, '89' for PICK-n-PULL Carson City).
Response
{
  "type": "object",
  "fields": {
    "vehicles": "array of vehicle objects with vin, make, model, year, row_number, date_added, vehicle_url, image_url",
    "yard_name": "string - Name of the yard location",
    "location_id": "integer - Yard location ID",
    "total_pages": "integer - Total pages available",
    "pages_fetched": "integer - Number of pages actually fetched",
    "total_results": "integer - Total vehicles at this yard",
    "vehicles_count": "integer - Number of vehicles returned in this response"
  }
}

About the Row52 API

What the API Returns

The get_yard_vehicles endpoint accepts a location_id (for example, 88 for PICK-n-PULL Windsor or 89 for PICK-n-PULL Carson City) and returns all vehicles currently listed at that yard. Each vehicle object includes vin, make, model, year, row_number, date_added, vehicle_url, and image_url. The response also carries yard-level metadata: yard_name, location_id, total_results, total_pages, pages_fetched, and vehicles_count.

Pagination Control

Row52 paginates inventory at 30 vehicles per page. By default the endpoint fetches all available pages, but the optional max_pages parameter lets you cap how many pages are retrieved. Setting max_pages to a small number is useful when you only need a recent sample of additions or want to reduce response time for large yards with hundreds of vehicles.

Data Freshness and Coverage

Inventory reflects the active Row52 listings for the requested yard. The date_added field on each vehicle lets you sort or filter by recency on your side. Because different Row52 partner yards use the same location-ID scheme, you can iterate over multiple location_id values to aggregate inventory across yards. The total_results field tells you how many vehicles exist at the yard regardless of how many pages you fetched.

Reliability & maintenanceVerified

The Row52 API is a managed, monitored endpoint for row52.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when row52.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 row52.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.

Last verified
5d ago
Latest check
1/1 endpoint passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Check whether a specific VIN is available at a nearby Row52 yard before making the trip
  • Build a make/model alert system by polling get_yard_vehicles and diffing the vin list over time
  • Aggregate multi-yard inventory using multiple location_id values to find the closest donor vehicle
  • Rank yards by freshness using date_added to identify which locations receive the most new arrivals
  • Map row-number data from row_number to yard layout diagrams for route planning inside the yard
  • Seed a parts-sourcing database with vehicle records that include both vehicle_url and image_url for reference
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 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.

Frequently asked questions
Does Row52 have an official developer API?+
Row52 does not publish a public developer API. There is no documented REST or GraphQL interface available to third parties on row52.com.
What does the `get_yard_vehicles` endpoint return for each vehicle?+
Each vehicle object contains eight fields: vin, make, model, year, row_number, date_added, vehicle_url, and image_url. The wrapping response also includes yard-level fields like yard_name, total_results, and total_pages so you can tell how much inventory exists beyond what you fetched.
Can I filter results by make, model, or year directly in the API?+
The get_yard_vehicles endpoint returns all vehicles at a yard without server-side filtering by make, model, or year. Filtering by those fields has to happen client-side after you receive the vehicle array. You can fork this API on Parse and revise it to add filter parameters that narrow the returned vehicle list before it reaches your application.
Does the API cover all Row52 yard locations, or only a subset?+
The endpoint works with any valid location_id in the Row52 network. You need to know the numeric ID for each yard you want to query; the API does not currently include a yard-directory endpoint that lists all valid location IDs and their names. You can fork this API on Parse and revise it to add a yard-listing endpoint that maps location IDs to yard names.
How current is the vehicle inventory returned by the API?+
The data reflects the live inventory listed on row52.com for the requested yard at the time of the request. Vehicles that have been pulled or sold may still appear briefly until the source listing is removed. Use the date_added field to identify recently arrived vehicles and handle stale records in your own logic.
Page content last updated . Spec covers 1 endpoint from row52.com.
Related APIs in AutomotiveSee all →
carvana.com API
Search Carvana's used car inventory by make, model, price, fuel type, and more. Retrieve paginated listings with pricing, specs, and delivery details, or fetch comprehensive information for a specific vehicle by ID.
autotrader.com API
Search Autotrader.com vehicle listings and access detailed information like pricing, specifications, and VIN data with flexible filtering options. Browse all available vehicle makes and models to refine your search across thousands of listings.
autobidmaster.com API
Search and browse vehicle auction inventory with detailed lot information, filters by make, type, body style, and damage condition, plus discover featured items and auction locations. Find the perfect vehicle by accessing comprehensive inventory data and exploring popular makes and damage types across AutoBidMaster auctions.
cars.com API
Search for vehicles on Cars.com using filters like price, make, and model, then get detailed specifications and dealer inventory information for any listing you're interested in. Access comprehensive vehicle details including pricing, features, and dealer contact information all in one place.
napaonline.com API
Search NAPA Auto Parts' catalog to find compatible parts by vehicle type, get detailed product information with reviews, and discover similar products all in one place. Browse by vehicle year, make, and model to quickly locate the right parts and read what other customers think about them.
oreillyauto.com API
Search O'Reilly Auto Parts inventory by product or vehicle compatibility to find parts, check real-time pricing and availability, and locate nearby stores. Discover the right parts for your specific vehicle year, make, and model with detailed product information and pricing.
car-part.com API
Search for recycled auto parts across thousands of vehicles and get detailed information on pricing, availability, and specifications from car-part.com. Find the exact parts you need with comprehensive search metadata and individual part details to compare options and locate the best deals.
riyasewana.com API
Browse vehicle listings from Sri Lanka's largest marketplace, search by category and filters, and access detailed information about specific cars, bikes, and other vehicles. Get comprehensive vehicle data including listings organized by category to find exactly what you're looking for.