Pet-care marketplace research
Mit Rover-Endpunkten verwandelst du pet-care marketplace research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Turn Rover's public marketplace listings into structured JSON — sitter and dog-walker search by location and service type, dog-trainer search, and normalized provider profiles carrying name, photo, bio, star rating, review count, repeat-client count, and years of experience. Credential-free.
Search Rover's public pet sitters, dog walkers, and trainers by location, and get normalized provider profiles with ratings and experience as JSON.
Endpunkt-Familien
4
Dokumentierte Parameter
14
Beispiele
4
Live-Katalog-Snapshot
Aktive Endpunkte
4
Methoden
GET
Pflichtparameter
9
Schema-Referenzen
4
{
"platform": "Rover",
"endpoint": "rover-sitter-search",
"method": "GET",
"path": "/rover/search",
"auth": "apiKey"
}Use Cases
Search Rover's public pet sitters, dog walkers, and trainers by location, and get normalized provider profiles with ratings and experience as JSON.
Mit Rover-Endpunkten verwandelst du pet-care marketplace research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Rover-Endpunkten verwandelst du provider supply and pricing analysis in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Rover-Endpunkten verwandelst du local service coverage mapping in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Rover-Endpunktkatalog — 4 Endpunkte, 14 dokumentierte Request-Parameter und 4 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
4 documented Rover endpoints, grouped into 4 request families — Search, Sitter and Trainer, plus 1 more.
14 request parameters are documented across those Rover endpoints, 9 of them required — the full input contract is public before you write any integration code.
4 of the 4 Rover endpoints ship a recorded example response, and 4 carry a documented response schema — you can code against the real JSON before the first request.
Rover endpoints document their error responses (400, 404, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
4 hosted MCP tools back the Rover endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/rover/search
/rover/sitter/{slug}
/rover/trainer/{slug}
/rover/trainer-search
Endpunktkatalog
/rover/searchSearches Rover's public sitter/walker listings by location and service type, returning sitter summaries (name, profile image, rating, review count, repeat-client count, years of experience, neighborhood/city/state, starting price, Star Sitter status, and a short bio).
Hinweise zur Response
- `slug` and the trailing path segment of `profile_url` are the value [`GET /rover/sitter/{slug}`](rover-sitter-profile.md) needs for profile detail lookup. - Rover silently falls back to an IP-derived location instead of erroring when `location` cannot be geocoded. This endpoint detects that fallback and returns a `400` invalid-params error instead of returning results for the wrong location. - A genuine zero-result search returns `sitters: []` with a `200`, distinct from a parser-drift or blocked-page failure, which returns a `503` instead. - `dog-training` and `on-demand-grooming` are not supported service types: Rover routes them through separate, unresearched search flows.
MCP-Tool rover_sitter_search
/rover/sitter/{slug}Returns a Rover sitter/walker profile: name, photo, bio, star rating, review count, repeat-client count, years of experience, neighborhood/city/state, starting price, Star Sitter status, the services offered with per-service pricing, and public review excerpts from the sitter's own profile page.
Hinweise zur Response
- Location is normalized to neighborhood/city/state, matching what Rover's own profile page shows — never an exact street address. - `reviews` reflects only the excerpts already public on the sitter's own profile page carousel. This endpoint does not aggregate a sitter's full review history. - `services` lists every service the sitter offers with its own starting rate, not just the service type used to find them in search.
MCP-Tool rover_sitter_profile
/rover/trainer-searchSearches Rover's public dog trainer listings by location, returning trainer summaries (name, profile image, headline, experience details, rating, review count, repeat-client count, years of experience, city/state/zip, starting price, training methodology, and skill/behavior tags).
Hinweise zur Response
- A genuine zero-result search returns `trainers: []` with a `200`, distinct from a parser-drift or blocked-page failure, which returns an error instead. - `starting_price` reflects a session's own base rate, not a package/bundle price. - The trailing path segment of a trainer's `profile_url` is what [`GET /rover/trainer/{slug}`](rover-trainer-profile.md) needs.
MCP-Tool rover_trainer_search
/rover/trainer/{slug}Returns a Rover dog trainer profile: name, photo, headline, experience and availability details, training methodology, rating, review count, repeat-client count, years of training, skill/behavior tags, and education credentials.
Hinweise zur Response
- `rating`/`review_count`/`repeat_client_count` are aggregated across every service the trainer offers on Rover (not Dog Training alone), matching what the trainer's own profile page displays. - This endpoint does not aggregate a trainer's full review history.
MCP-Tool rover_trainer_profile
Verwandte APIs
Marketplaces & Retail
Research new, used, and vintage instruments across Reverb listings, seller shops, and the Price Guide. Keep current asking prices separate from historical sales, and preserve model, finish, year, condition, and currency when comparing gear.
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
So scrapst du Rover
Crawlora's Rover endpoints return normalized public Rover listing data as JSON with one API key — no Rover account required. Sitters/walkers and trainers are separate listing types with their own search and profile endpoints.
Call /rover/search with a location and service type for normalized pet-sitter and dog-walker summaries — name, profile image, headline facts, and the slug each profile lookup takes.
Pass a slug to /rover/sitter/{slug} for that provider's normalized profile: name, photo, bio, star rating, review count, repeat-client count, and years of experience.
Call /rover/trainer-search with a location for Rover's dog-trainer listings — a separate listing type from sitters and walkers, with its own summaries.
Pass a slug to /rover/trainer/{slug} for that trainer's normalized profile, including headline, experience and availability details, training methodology, and star rating.
FAQ
Call /rover/search for sitters and walkers or /rover/trainer-search for dog trainers, then /rover/sitter/{slug} or /rover/trainer/{slug} for one provider's normalized profile — all return structured JSON with one API key.
No — they are separate marketplaces on Rover with their own search and profile endpoints. Use /rover/search plus /rover/sitter/{slug} for pet sitters and dog walkers, and /rover/trainer-search plus /rover/trainer/{slug} for dog trainers.
Name, photo, bio, star rating, review count, repeat-client count, and years of experience for sitters and walkers; trainers additionally carry headline, availability details, and training methodology.
No — these endpoints read Rover's public listing pages, so one Crawlora API key is all that's required. Collect only public data you are authorized to use.