Outdoorsy Scraper: Up to 1,000 Free Results a Month (2026)

Each listing record carries 89 fields, including nightly, weekly, and monthly base rates in USD. You can extract full vehicle specifications, sleeping capacities, and mileage policies for over 100,000 RVs across the USA, Canada, UK, Australia, and Europe. This is built for travel marketplace developers and price intelligence analysts who need vehicle specs and owner response rates, but it does not return tax or booking fee breakdowns. The data includes amenities, photo URLs, and owner dealer status. This Actor is for those building rental catalogs or supply reports, but is not for users who need exact street addresses which are unavailable.

Try it: open Outdoorsy Scraper on Apify, sign in on the free plan and run the prefilled example.

Can you try Outdoorsy Scraper before paying?

Yes. Apify's free plan includes $5.00 of prepaid usage every month and asks for no credit card. At $0.005 per result, that covers up to 1,000 results of Outdoorsy Scraper a month, before run-start charges and platform usage.

The example request further down caps maxItems at 10, so a first run returns at most 10 results and costs at most $0.05 in result charges. That is enough to see the real shape of the data before deciding anything.

Outdoorsy Scraper was last updated on 2026-08-14. It is one of 1,729 Actors CrawlerBros publishes on Apify, which together have 754,756 lifetime public runs and an average rating of 4.63 out of 5 across 416 reviews.

What does it cost to run Outdoorsy Scraper?

Each result costs $0.005 on Apify's free plan, which is $5.00 per 1,000 results. Starting a run is charged separately at $0.005 per GB of Actor memory. Apify also bills the platform usage each run consumes, at the rates of your Apify plan, on top of these charges.

The maxItems control is the primary setting that dictates the result charges, as you pay for each item written to the dataset. To keep the initial result charge at $0.05, use the example input which limits the run to 10 items.

How do you run Outdoorsy Scraper from the API?

The schema marks 1 of its 20 controls as required: mode. Every value in the payload below comes from the published schema's own prefills, which means you can paste it, swap the token, and get a real result.

Call the synchronous endpoint to start a run and receive dataset items in one request:

curl -X POST "https://api.apify.com/v2/acts/crawlerbros~outdoorsy-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"search","maxItems":10,"proxyConfiguration":{"useApifyProxy":true}}'

The same run from Python, using the official client:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")

run_input = {
  "mode": "search",
  "maxItems": 10,
  "proxyConfiguration": {
    "useApifyProxy": True
  }
}

run = client.actor("crawlerbros~outdoorsy-scraper").call(run_input=run_input)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

And from Node.js:

import { ApifyClient } from 'apify-client'

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' })

const input = {
  "mode": "search",
  "maxItems": 10,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

const run = await client.actor('crawlerbros~outdoorsy-scraper').call(input)
const { items } = await client.dataset(run.defaultDatasetId).listItems()
console.log(items)

That endpoint blocks until the run completes. Fine while you are testing a handful of records, risky once a run takes minutes: a dropped connection loses the response even though the run itself finished. Switch to an asynchronous start with polling or a webhook before you schedule anything.

Which Outdoorsy Scraper inputs matter, and which can you skip?

The mode control is the required field that changes whether the Actor returns listing details or owner profiles. Most users will use searchQuery to define their geographic target while using filters like rvType to narrow the vehicle results.

• mode (string): What to fetch. Default: "search".
• maxItems (integer): Hard cap on emitted records. Default: 50.
• proxyConfiguration (object): Optional proxy. Outdoorsy generally does not require a proxy; if a request is blocked (403/429), the actor automatically retries it through this proxy.
• searchQuery (string): City, region, or destination - e.g. Austin, Texas, Los Angeles, CA, Yosemite National Park, United States. Also accepts a country name. Default: "United States".
• rvType (string): Only emit rentals of this RV type (mode=browseByRvType requires it; mode=search uses it as a filter).
• searchAddress (string): Geographic area to search within (city, region, or country). Defaults to United States. Default: "United States".
• listingUrls (array): Outdoorsy listing page URLs, e.g. https://www.outdoorsy.com/rv-rental/austin_tx/2021_winnebago_12345-listing (bare listing IDs also accepted). Default: [].
• ownerRefs (array): Outdoorsy owner profile URLs, e.g. https://www.outdoorsy.com/users/4589700 (bare numeric owner IDs also accepted). Default: [].
• country (string): Only emit listings located in this country or region.
• minPrice (number): Only emit listings with a nightly price at or above this amount in USD.
• maxPrice (number): Only emit listings with a nightly price at or below this amount in USD.
• minRating (number): Only emit listings with an average rating at or above this value (0-5). Default: 0.

The other 8 controls, with their defaults, are listed in the input schema on Outdoorsy Scraper on Apify.

Fixed-choice controls: mode accepts search (Search RV rentals), browseByRvType (Browse all rentals by RV type), byUrl (Fetch listings by URL), ownerProfile (Scrape owner profiles); rvType accepts 10 values, including "" (Any RV type), classA (Class A motorhome), classB (Class B motorhome (camper van)), classC (Class C motorhome); country accepts "" (Any country), US (United States), CA (Canada), UK (United Kingdom), AU (Australia), EU (European Union).

What does Outdoorsy Scraper return?

The records are ideal for supply analysis and building rental catalogs because they include granular specs like vehicleWeight and deliveryRadiusMiles. The output conspicuously does not contain real-time availability calendars beyond the selected date window.

Output per listing

• listingId, name, slug, sourceUrl
• vehicleType (Class A / Class B / Travel trailer / …), type, rentalCategory
• vehicleClass, vehicleBodyClass, vehicleMake, vehicleModel, vehicleYear, vehicleTitle, vehicleLicensePlateState
• vehicleLength, vehicleLengthWithHitch, vehicleWidth, vehicleHeight, vehicleDryWeight, vehicleGvwr, vehicleAmps, vehicleBoxLength
• sleeps, sleepsAdults, sleepsKids, seatbelts, beds[] (e.g. Queen x1)
• pricePerDay, pricePerWeek, pricePerMonth (USD), plus lowPricePerDay, minBundleDayPrice
• weeklyDiscount, monthlyDiscount, minimumDays, securityDeposit, prepFee, currency
• city, state, county, country, zip, latitude, longitude, distanceMiles
• rating, reviewCount, communicationScore, cleanlinessScore, mechanicalScore, valueScore, groupReviewScore
• amenities[] (pet friendly, generator, Wi-Fi, air conditioner, solar panels, …)
• ownerUserId, ownerName, ownerResponseRate, ownerScore, ownerIsDealer, ownerIsPro, ownerAvatarUrl, ownerProfileUrl
• deliveryAvailable, deliveryRadiusMiles, deliveryPricePerMile
• mileageIncludedPerDay, mileageUnlimited, mileageUnit, extraMilePrice
• instantBook, allowsLongTerm, cancelPolicy, cancelText, checkIn, checkOut
• summary, description, houseRules, hostNotes, tags[]
• primaryImageUrl, photoUrls[] - all listing photo URLs
• reviews[] - up to 10 reviews with scores and dates (mode=byUrl with includeReviews)
• completedTripsCount, requestCount90d, favoriteCount, rentalViewsLast30Days, created, updated
• recordType: "listing", scrapedAt

Output per owner profile (mode = ownerProfile)

• ownerUserId, ownerName, firstName, lastName, avatarUrl, ownerProfileUrl, sourceUrl
• isDealer, isPro, isGuest, isOwner
• responseRate (%), averageResponseTime, medianResponseTime, ownerScore
• ownerReviewsCount, reviewsCount, yearsOwned, yearsRVing
• businessName, businessDescription, businessWebsite, description, experience
• cancelPolicy, localeLanguage, localeBaseCurrency, created, social[]
• listings[] - the owner's other rentals: {listingId, name, vehicleType, pricePerDay, rating, reviewCount, city, state, primaryImageUrl, sourceUrl}
• recordType: "ownerProfile", scrapedAt

These are the documented fields. Optional ones can be empty on a given record, so measure how often each field your deliverable depends on is populated across a real sample before automating the handoff.

How do you build the workflow end to end?

Open Outdoorsy Scraper and work through these in order. Each step ends with something to check, so a bad configuration surfaces on a small run rather than a scheduled one.

1. Select the operational mode using the mode parameter, choosing from search, browseByRvType, byUrl, or ownerProfile.
2. Enter a geographic target into the searchQuery field if you are using search mode to identify listings in specific cities or regions.
3. Apply vehicle filters by setting rvType to a value like classC or travelTrailer to narrow the inventory to specific RV categories.
4. Set maxItems to 10 for your initial run to verify that the 89 listing fields meet your requirements while keeping result charges at $0.05.
5. Check the dataset output to confirm that pricePerDay and vehicleMake are populated for your target market.
6. Narrow results using the minPrice and maxPrice filters if your initial geographic search returns more than the 1,000 listing cap.
7. Enable includeReviews when mode is set to byUrl if you need the scores and dates for the 10 most recent reviews per listing.
8. Monitor the recordType field in the final dataset to distinguish between listing records and ownerProfile records.

How do you apply it? Three worked playbooks

These are Outdoorsy Scraper's own documented use cases, each worked through as an operating pattern rather than a description.

Use case 1: Travel marketplaces

Outcome: Build complete RV rental catalogs with pricing and vehicle specs

Configure: Set mode to "search", searchQuery to "United States", and maxItems to 1000.

Working method: Initiate a country-level search to capture a broad cross-section of available inventory. Once the initial dataset is retrieved, group the results by vehicleType to determine which regions have the highest density of specific RV classes.

Deliverable: A structured dataset containing specs, sleeping capacity, and amenity arrays for up to 1000 RV listings.

Stop condition: The resulting dataset contains fewer than 5 records for a major metropolitan area.

Use case 2: Price intelligence

Outcome: Track nightly/weekly/monthly rates, discounts, and deposits by region

Configure: Set mode to "browseByRvType", rvType to "classB", and searchAddress to "Austin, Texas".

Working method: Run the Actor using a specific geographic searchAddress to isolate a local market. Examine the pricePerDay, weeklyDiscount, and monthlyDiscount fields to calculate the effective rate for different rental durations.

Deliverable: A report detailing base rates, securityDeposit amounts, and discount structures for a specific vehicle class.

Stop condition: The recordType field returns ownerProfile when listing data was expected.

Use case 3: Competitor research

Outcome: Analyze top-rated owners, response rates, and fleet sizes

Configure: Set mode to "ownerProfile" and enter profile URLs into the ownerRefs array.

Working method: Submit a list of owner profile URLs into ownerRefs to fetch individual performance metrics. Use the nested listings array within each owner profile record to calculate the total count and average rating of their managed fleet.

Deliverable: A spreadsheet of owner responseRate, ownerScore, and fleet details for identified competitors.

Stop condition: The responseRate field is omitted from more than 50% of the retrieved profiles.

What breaks, and how do you design around it?

• Search results cap: the marketplace caps a single query's result set near 1000 listings; maxItems is the hard output cap (max 1000).
• Pricing: all price fields are nightly/weekly/monthly base rates in USD as shown by the marketplace, excluding taxes and booking fees. Some listings use custom pricing; minBundleDayPrice reflects the cheapest configured rate.
• Price/rating filters are applied against the data Outdoorsy returns (a listing without a published rate or rating passes the corresponding filter rather than being dropped).
• Availability window: startDate/endDate filter to listings bookable in that window; listings without published availability pass through.
• Reviews: fetched on demand in byUrl mode (includeReviews) - up to 10 reviews per listing.
• Camper vans are grouped under Class B on Outdoorsy; the camperVan RV type maps to the same bucket.
• rvType accepts display spellings too (Class C, travel trailer, fifth wheel, pop-up, …) - they are normalized to the canonical enum keys before querying.
• Inverted ranges are rejected up front: if minPrice > maxPrice (or minRating > 5, etc.) the run exits with a clear status message instead of burning API calls.
• Owner profiles carry both ownerProfileUrl and the project-standard sourceUrl.
• Not affiliated: this actor is a third-party tool and is not affiliated with or endorsed by Outdoorsy.

When the 1,000 listing cap is reached for a single search query, you can capture more data by using narrower filters like rvType or minPrice. If specific pricing fields are unavailable, they are omitted from the record rather than filled with placeholders.

When should you not use Outdoorsy Scraper?

Do not use this Actor if you require every single listing in a massive region like the United States in a single run, as search results are capped near 1,000 listings per query. If your project specifically targets peer-to-peer rentals on other platforms, RVshare Rentals & Owner Listings Scraper is the appropriate alternative. For broader vacation rental data including stationary homes and apartments, you should instead use Airbnb Scraper or Vrbo Vacation Rentals. This tool is also not suitable for those requiring historical pricing trends, as it scrapes live data as it appears on Outdoorsy at the time of the run.

What should you check before trusting the output?

• Verify that the currency field matches the expected market, as Outdoorsy displays prices in USD for the US site.
• Check that ownerUserId is present in listing records to ensure you can link vehicles to their respective owner profiles.
• Stop the run if the result count is zero despite a broad searchQuery, as this suggests the filters like minRating may be too restrictive.
• Validate that primaryImageUrl starts with a valid URL protocol before passing the data to an image processing pipeline.
• Ensure latitude and longitude fields are populated if your application requires geographic mapping of the rentals.

None of this proves a record is correct. It gives a scheduled Outdoorsy Scraper run defined points where it should stop instead of quietly passing bad data downstream.

Frequently asked questions

How much does it cost to scrape 1,000 listings on the free plan?

On Apify's free plan, 1,000 results cost $5.00 in result charges. This is because the free-plan price is $0.005 per result. Apify's free plan includes $5.00 of monthly usage, which covers those 1,000 results before accounting for the run-start fee of $0.005 per GB of Actor memory and other platform usage costs.

Is there a limit to how many listings I can get per search?

The marketplace caps a single query's result set near 1000 listings. To stay within this limit, the maxItems control is used as a hard output cap with a maximum of 1000. For very broad areas, you may need to use filters like rvType to capture all available listings.

Does the scraper return the location of the RV?

Yes, the scraper returns several location fields including city, state, county, country, zip, latitude, and longitude. These fields are included in the 89 fields documented for listing output. It does not provide the exact street address as that is not part of the public listing data.

Can I filter results by specific dates?

You can use the startDate and endDate filters to limit listings to those bookable in that window. Listings without published availability pass through these filters. This allows you to target specific trip windows when building travel marketplace catalogs or trip planning apps.

Why are some fields like ownerResponseRate missing?

Fields that are unavailable are omitted rather than filled with placeholders. Owners on Outdoorsy publish different amounts of data, and some may hide their mileage policy or have no reviews yet. If a piece of data is not on the marketplace page, it will not appear in your dataset.

Where to go next

When you are ready to run it, open Outdoorsy Scraper on Apify; the free plan covers up to 1,000 results a month.

Start with the Outdoorsy Scraper Actor page for the current input schema, pricing tier, and run history.

Other Actors we maintain for related data:

• RVshare Rentals & Owner Listings Scraper: Scrape RVshare RV rental listings by location, get RV details, and scrape owner profiles with all their rental listings.
• Vrbo Vacation Rentals: Scrape Vrbo vacation-rental listings by destination and dates.
• Airbnb Scraper: Scrape Airbnb listings, prices, ratings, host info, coordinates and photos for any location.
• Apartment List Scraper: Scrape Apartment List - the US apartment rental marketplace.
• Hipcamp Campsites & Host Scraper: Scrape Hipcamp campsite listings, host profiles, and public campgrounds.
• Boliga Scraper - Danish Property Listings: Scrape boliga.dk, Denmark's leading property portal.
• Apartments.com Scraper: Scrape rental listings from Apartments.com with search by location, bedroom count, price, property type, and amenities.
• Furnished Finder Scraper: Extract furnished rental listings from FurnishedFinder.com by city and state.

Related guides:

• Airbnb Scraper: 3 Practical Use Cases
• Guide to Furnished Finder Data Extraction for Rental Markets
• Spotahome Mid-Term Rentals Scraper: 92 Cities Covered (2026)
• Sedo Domain Marketplace Scraper: 16 Data Fields per Record (2026)

Resources

• Actor documentation, input schema, and pricing: verified against the published Actor on 2026-10-07.

• Actor last updated by its maintainers on 2026-08-14.

• Run outcome figures cover the 30 day public window ending 2026-10-07.

• Outdoorsy Scraper on Apify