PlugShare check-ins

GET https://api.api.sh/plugshare/v1/location/reviews
1 credit / call automotive try it in the playground →

A location's check-ins, newest first: date, result (charged, could not charge, comment), comment, problem reported, connector, kW, amps, volts, vehicle, helpful votes, the network's reply, and the member's public display name. Pass next_page back as page; null on the last page.

Every response includes credits_used: the credits this call cost.

Part of the PlugShare API: 10 endpoints with prices, use cases and example responses.

Parameters

nametypedescription
idrequired string PlugShare location id or a plugshare.com/location/<id> link. Example: 98734
page integer Page number (default 1).
limit integer Check-ins per page (1-50, default 25). Example: 25

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/plugshare/v1/location/reviews?id=98734" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

Example response (real call, trimmed: lists cut to 2 items, long text shortened, raw left out)

{"id": 98734,"page": 1,"count": 25,"reviews": [{"id": 12279908,"created_at": "2026-08-24T17:26:22Z","finished_at": null,"rating": -1,"result": "could not charge","comment": "both chargers could not communicate with my car.\nworked last Thursday","language": "eng","problem": 4,"problem_description": "Could not activate","connector_id": 13,"connector": "CCS1","kilowatts": null,"amps": null,"volts": null,"waited": false,"vehicle": "BMW i3","vehicle_make": "BMW","helpful": 0,"user": "anotherEd","user_name": "anotherEd","user_photo": null,"owner_response": {"title": "EVgo Response","message": "We’re so sorry you were unable to charge. After doing some research into the station history, we saw there were successful charges before an…","created_at": "2026-08-24T18:05:02Z"}},{"id": 10868162,"created_at": "2025-06-24T02:19:54Z","finished_at": null,"rating": -1,"result": "could not charge","comment": "There's no Tesla cable even though it says Tesla","language": "eng","problem": 1,"problem_description": "Broken hardware","connector_id": null,"connector": null,"kilowatts": null,"amps": null,"volts": null,"waited": false,"vehicle": "Tesla Model 3","vehicle_make": "Tesla","helpful": 0,"user": "Jessica G.","user_name": "Jessica Gliddon","user_photo": null,"owner_response": {"title": "EVgo Response","message": "We apologize for the inconvenience and appreciate you reporting the issue you encountered with the charger. We have forwarded this issue to …","created_at": "2025-06-25T04:41:30Z"}},"… 23 more"],"next_page": 2,"cached": false,"credits_used": 1}
The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.