PlugShare EV Charging Station Scraper: $5.00 per 1,000 Results (2026)

Station records carry 38 fields on the charging station output group, including community PlugScore ratings, outlet-level power specs, and driver check-in logs. The dataset provides real-time community availability and hardware failure reports alongside network pricing. Extraction costs $5.00 per 1,000 results on the free plan, which covers both geographic radius searches and direct station lookups. This tool is built for fleet operators and route planners requiring driver-verified reliability data, not for users seeking private contact details of reviewers, which the platform does not expose.

Try it: open PlugShare EV Charging Station Scraper on Apify, sign in on the free plan and run the prefilled example.

Can you try PlugShare EV Charging Station 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 PlugShare EV Charging Station Scraper a month, before run-start charges and platform usage.

PlugShare EV Charging Station Scraper was last updated on 2026-07-21. It is one of 1,724 Actors CrawlerBros publishes on Apify, which together have 716,703 lifetime public runs and an average rating of 4.63 out of 5 across 416 reviews.

What does it cost to run PlugShare EV Charging Station 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.

Total run charges depend directly on the number of records emitted to the dataset, which is controlled by maxItems and your geographic search filters. Nested fields like embedded reviews or user photos do not increase the per-result pricing. Test query boundaries using a small radiusKm and a low maxItems setting to validate record coverage before widening search radii.

How do you run PlugShare EV Charging Station Scraper from the API?

The schema marks 1 of its 25 controls as required: mode. Nothing in the payload below is illustrative. Those are the schema's prefilled defaults for PlugShare EV Charging Station Scraper, so the request works once your token is in place.

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~plugshare-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"search"}'

The same run from Python, using the official client:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")

run_input = {
  "mode": "search"
}

run = client.actor("crawlerbros~plugshare-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"
}

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

Because the call is synchronous, your client waits for the whole run. Keep it for exploration. For scheduled work, start the run without waiting and collect the dataset afterwards, so network trouble costs you a retry rather than the results.

Which PlugShare EV Charging Station Scraper inputs matter, and which can you skip?

The mode selector determines whether the Actor performs a coordinate search, fetches specific locations by ID, or flattens reviews and photos. For standard discovery, configure locationQuery or latitude and longitude alongside radiusKm to set the boundary. Optional filters like connectorTypes, networks, and minPowerKW refine the match criteria and should be left blank on initial exploratory runs.

• mode (string): What to fetch. Default: "search".
• locationQuery (string): Free-text place name to search near (city, address, landmark). Geocoded automatically. Ignored if latitude/longitude are set. Default: "Los Angeles, CA".
• latitude (number): Exact search-center latitude. Overrides locationQuery when set together with longitude.
• longitude (number): Exact search-center longitude. Overrides locationQuery when set together with latitude.
• radiusKm (integer): Only emit stations within this distance of the search center (mode=search). Default: 25.
• stationIds (array): Numeric PlugShare location IDs, e.g. 7057, or full PlugShare station URLs, e.g. https://www.plugshare.com/location/7057 (either form works). Default: [].
• connectorTypes (array): Only emit stations offering at least one of these connector types (mode=search). Default: [].
• networks (array): Only emit stations on these charging networks (mode=search). Curated list of common networks - a station's own networks output field is populated regardless of this filter. Default: [].
• minPowerKW (integer): Drop stations whose fastest outlet is below this power.
• maxPowerKW (integer): Drop stations whose fastest outlet is above this power.
• accessType (string): Which access levels to include. Default: "publicAndRestricted".
• freeOnly (boolean): Only emit stations with no published charging cost. Default: false.

The other 13 controls, with their defaults, are listed in the input schema on PlugShare EV Charging Station Scraper on Apify.

Fixed-choice controls: mode accepts search (Search by location), byId (Lookup stations by ID), reviews (Community reviews / check-ins by station ID), photos (User photos by station ID); accessType accepts publicOnly (Public only), publicAndRestricted (Public + Restricted (default PlugShare browsing)), all (Public + Restricted + Private Home).

What does PlugShare EV Charging Station Scraper return?

Output records supply granular physical charger details, real-time outlet availability states, and timestamped driver check-in logs with reported hardware issues. They do not contain private user email addresses or phone numbers, as PlugShare publishes only public display names. The structure fits geospatial mapping, charger uptime monitoring, and network benchmarking systems.

Output per charging station (mode=search / byId)

• locationId, sourceUrl - PlugShare's station page
• name, address, latitude, longitude, distanceKm (mode=search)
• poiType - e.g. "Parking Garage/Lot", "Shopping Center"
• accessType - Public / Restricted / Private Home
• accessRestrictions[] - e.g. "Tesla Only", "Customers Only"
• status, comingSoon, underRepair, confidenceLevel
• stationCount, connectorTypes[], isFastCharger
• hasCost, costDescription, hasDynamicPricing
• parkingType, parkingAttributes[], amenities[]
• open247, regularHours, phone, overheadClearanceMeters
• plugscore - PlugShare's 0-10 community confidence rating
• totalReviews, totalPhotos
• networks[] - distinct charging-network operators on site
• stations[] - one entry per physical charging point: stationId,
• reviews[] - community check-ins: reviewId, createdAt, rating,
• photos[] - photoId, photoUrl, thumbnailUrl, thumbnailUrl2x,
• createdAt, updatedAt
• recordType: "chargingStation", scrapedAt

Output per review (mode=reviews)

• locationId
• locationName
• sourceUrl
• stationId

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 PlugShare EV Charging Station 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 mode search, provide a target city in locationQuery or precise latitude and longitude coordinates, and set radiusKm to your target search area.
2. Apply technical station filters such as connectorTypes and minPowerKW to exclude plugs incompatible with your target fleet or vehicle specifications.
3. Set accessType to publicOnly if you need to eliminate restricted-access and private residential plugs from the dataset.
4. Configure minPlugscore and minReviewCount to drop low-rated or unverified community locations before fetching full payloads.
5. Toggle includeReviews and includePhotos to true, setting maxReviewsPerStation and maxPhotosPerStation to your required depth per site.
6. Set maxItems to a small test threshold such as 5 and execute a preliminary run to verify that the returned fields match your data schema.
7. Inspect the resulting records in the dataset to confirm that nested fields like stations, outlets, and reviews populated as expected.
8. Widen maxItems up to the 500 endpoint limit or switch to mode byId with an array of stationIds to pull deeper history across identified target sites.

How do you apply it? Three worked playbooks

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

Use case 1: EV route planning tools

Outcome: Layer in real driver-confirmed

Configure: Set mode to search, locationQuery to target corridor checkpoints, connectorTypes to ["ccs1", "nacsTesla"], availableNowOnly to true, and maxItems to 50.

Working method: Execute geographic corridor queries across designated waypoints. Compare real-time availableCount across the stations array against the static stationCount to verify operational redundancy.

Deliverable: A filtered GeoJSON or tabular dataset of confirmed active high-speed charging hubs along specific transit routes.

Stop condition: Zero stations returned across multiple search checkpoints indicating overly narrow power or connector filters.

Use case 2: Trust & reliability research

Outcome: Surface reported problems and

Configure: Set mode to reviews, populate stationIds with a list of monitored site IDs, and set maxReviewsPerStation to 50.

Working method: Pull community check-in history directly by station ID. Filter review entries on ratingLabel equal to Reported Problem and evaluate problemType alongside operatorResponse fields to measure failure frequencies.

Deliverable: A historical reliability incident log detailing recurring hardware breakdowns and operator resolution rates per charging network.

Stop condition: Scraped station IDs returning empty review arrays due to invalid location IDs or unreviewed private points.

Use case 3: Market research

Outcome: Compare community sentiment (PlugScore, review

Configure: Set mode to search, locationQuery to a metropolitan region, accessType to publicOnly, includeReviews to false, and maxItems to 200.

Working method: Scan metropolitan regions without nested review objects to capture broad footprints quickly. Group returned records by the networks field and aggregate plugscore, totalReviews, and totalPhotos metrics across operators.

Deliverable: A comparative regional benchmark report charting average PlugScore confidence and physical charger density by operating network.

Stop condition: Search radius returns the maximum 500-item API limit, signaling the need to partition into smaller coordinate grids.

What breaks, and how do you design around it?

PlugShare caps geographic search results at 500 locations per API request. To extract larger regions, divide geographic territories into smaller coordinate grids using latitude and longitude rather than large radius searches. Community fields like plugscore and reviews remain empty for newly registered stations lacking driver check-ins, so ingest pipelines must handle missing sentiment fields gracefully.

When should you not use PlugShare EV Charging Station Scraper?

Do not use this Actor if you require an exhaustive directory of static infrastructure where driver feedback and real-time status are irrelevant. In scenarios needing static global directory records without community reviews or check-in telemetry, an open-access directory source is more suitable. If you require private host contact details for home chargers, look elsewhere because the API excludes private contributor personal data. For broader point-of-interest mapping across international locations outside EV infrastructure, consider specialized local engines such as Naver Map Scraper instead.

What should you check before trusting the output?

• Verify that the plugscore field is non-null when evaluating community quality, dropping records with omitted scores if baseline driver validation is required.
• Confirm that the stations array contains at least one entry with an outlets list detailing valid connectorType and kilowatts values.
• Inspect ratingLabel inside reviews to ensure values conform to expected categories like Confirmed Working, Reported Problem, or Comment.
• Check that lastAvailabilityUpdate under each physical station entry contains a valid ISO timestamp before using outlet availability status in routing logic.
• Abort downstream ingestion if maxItems returns zero records due to overly restrictive connectorTypes or networks filter combinations.

None of this proves a record is correct. It gives a scheduled PlugShare EV Charging Station 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 PlugShare charging stations?

Results cost $0.005 per record, which equals $5.00 per 1,000 results on the free plan. Apify's free plan includes $5.00 of monthly usage without a credit card, covering up to 1,000 results before standard platform usage fees. Paid Apify tiers offer lower per-unit result costs.

Can I search by exact geographic coordinates instead of city names?

Yes. Provide latitude and longitude in the input schema. When numeric coordinates are supplied together, they automatically override the locationQuery string, allowing you to scan custom bounding boxes or route corridors without relying on text geocoding.

How does the scraper handle missing community reviews or photos?

PlugShare relies on user-submitted contributions, meaning newly registered or rural stations may lack check-in activity. The Actor omits empty fields like reviews, photos, and plugscore when no community data exists, preserving clean records without null clutter.

Can I extract only reviews without full station details?

Yes. Switch the mode setting to reviews and pass a list of station IDs or URLs into the stationIds parameter. The Actor will return flattened review records containing user feedback, problem classifications, and vehicle models.

What is the maximum number of stations returned in a single search?

The underlying API caps search responses at 500 stations per query, setting the maximum value for maxItems to 500. To gather more stations across a large state or country, run separate searches targeting distinct coordinate centers.

Where to go next

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

Start with the PlugShare EV Charging Station Scraper Actor page for the current input schema, pricing tier, and run history.

Other Actors we maintain for related data:

• Naver Map Scraper: Search places by keyword or fetch specific places by URL, and get full business details: address, phone, hours, menus, photos, amenities, transit access, and review metrics.
• Rover Sitter Scraper: Scrape Rover.com with search pet care providers by service type and location.
• FlixBus Scraper: Scrape FlixBus - Europe and North America's largest intercity bus network.
• Amtrak Scraper: Scrape Amtrak - America's intercity passenger rail network.
• OpenTable + Resy Scraper: Scrape restaurant data from OpenTable and Resy in a single actor.
• AeroLOPA Seat Map Scraper: Scrape AeroLOPA.com airplane seat maps - seat pitch, width, recline, and AeroLOPA's own seat quality ratings per cabin class, browsable by airline or aircraft type.
• Crowd Supply Scraper: Scrape Crowd Supply (crowdsupply.com) - a crowdfunding platform focused on open-source hardware and electronics.
• Coworker Space Scraper: Scrape coworker.com - the world's largest coworking-space directory.

Related guides:

• BillionGraves Scraper: 47 Data Fields, Up to 1,000 Free Results/Month
• Kiwi.com Scraper: Up to 1,000 Free Results a Month (2026)
• Applying StockTwits Scraper: 3 Proven Workflows and Setup Guides

Resources

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

• Actor last updated by its maintainers on 2026-07-21.

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

• PlugShare EV Charging Station Scraper on Apify