Scrappa API docs and endpoint search

Perform a Google search and get structured results using the same reliable Google retrieval path as Search Advanced. gl=us and hl=en are used when omitted. page is 0-based: page=0 is the first page and page=1 is the second; start is the preferred explicit result offset. total_results is Google's estimate when exposed and may be null; organic_results_count is the number of returned organic rows. Scrappa does not impose fixed per-key concurrency or requests-per-minute limits. Transient capacity responses include Retry-After, and failed responses including 503 are never charged. External text is returned as valid UTF-8; malformed byte sequences are replaced with the Unicode replacement character (�), while valid Unicode is preserved. Account balance and recent usage are available from GET /api/account/usage and in the dashboard. YouTube results include raw views/date text plus normalized view_count and publication_age when Google provides them.

Fetch a dedicated Google AI Overview for a query. Unlike Search Advanced, this endpoint always requests Google AI Mode and returns the generated answer as plain text plus customer-renderable markdown, structured text blocks (paragraphs, headings, lists, equations), cited sources/quotes, and header images when Google produces them. Queries that do not yield a parseable AI Overview after retries return an unbilled 503. This is a separate product from the best-effort ai_overview field on Search Advanced.

Fetch a modern Google SERP and return richer structured modules including organic results, ads, People Also Ask, knowledge panels, local packs, news, videos, images, shopping blocks, answer boxes, related searches, spelling corrections, filters, and pagination when present. gl=us and hl=en are used when omitted. page is 0-based: page=0 is the first page and page=1 is the second; start is the preferred explicit result offset. total_results is Google's estimate when exposed and may be null; organic_results_count is the number of returned organic rows. Scrappa does not impose fixed per-key concurrency or requests-per-minute limits. Transient capacity responses include Retry-After, and failed responses including 503 are never charged. External text is returned as valid UTF-8; malformed byte sequences are replaced with the Unicode replacement character (�), while valid Unicode is preserved. Account balance and recent usage are available from GET /api/account/usage and in the dashboard. Explicit empty SERPs return immediately without provider retries, and tbs and as_qdr date filters use bounded retries. Source links are resolved when Google exposes their destinations; unavailable question source links are omitted. Video cards are returned in inline_videos; YouTube cards include channel, raw views and date text, normalized view_count, and publication_age when Google provides the metadata. AI Overview extraction is best effort: ai_overview is populated only when the module is present in the captured HTML. The endpoint does not wait for asynchronously inserted AI Overviews, make a secondary Google AI Overview request, or expand the module, and no request parameter enables those behaviors. When captured, cited sources are returned in ai_overview.references; null means the module was absent from the captured response, not that Google never displays one for the query. Local-pack-only responses are returned with empty organic_results and remain unbilled; they do not substitute for missing site-filtered results. Responses for a different query and non-definitive responses without usable result modules after retries return an unbilled 503. Local places include an optional website field when Google provides a valid business website action. search_url contains the sanitized Google SERP URL that produced the response. The serp_results collection preserves the DOM order of supported paid cards, local modules, and organic cards. rank_group is the 1-based position within one type; rank_absolute is the 1-based position across those supported types. A multi-place local module occupies one rank_absolute slot, and every nested local_results.places item inherits that rank so clients can merge local and organic results and sort by rank_absolute.

Lightweight web search endpoint. Returns structured JSON search results. Max 200 results per query (10 pages × 20 results). Supports query modifiers like filetype:pdf, site:reddit.com, or "exact phrase". YouTube results include views, view_count, date, and publication_age when the active provider supplies that metadata. The people_also_search_for field is a best-effort autocomplete enrichment and may be empty; use Search Autocomplete when suggestions are required.

Get search suggestions for a query prefix. Returns up to 10 suggestions based on popular searches.

Streamlined service for basic searches of locations, places, and points of interest on Google Maps.

Perform detailed searches for locations, places, and geographic data with advanced filtering options including coordinates, zoom level, result limits, and pagination.

The Google Maps Autocomplete API provides automatic query predictions as users type. Helps users find places, addresses, and points of interest quickly. Accepts both "q" and "query" parameters for consistency with other autocomplete endpoints.

Fetch business details directly from Google Maps including contact info, hours, photos, and the first-party Google reviews summary. The review_count and reviews_per_rating fields exclude syndicated reviews and align with the unique Google Reviews items where is_google_review is true.

Get directions between two locations with route information including distance, duration, and step-by-step navigation. Supports driving, walking, bicycling, and transit modes.

Google Reviews API documentation for developers who need Google Maps place reviews in structured JSON. Scrappa's GET /api/maps/reviews endpoint fetches review text, star ratings, reviewer profile fields, timestamps, photos, language, review form attributes, review links, likes, and owner responses from public Google Maps business listings. ## Google Maps reviews API for business review data Use this endpoint when you already have a Google Maps business_id and need reviews for reputation monitoring, local SEO research, review analytics, customer sentiment analysis, lead enrichment, or competitive benchmarking. It is built for Google Maps reviews scraping workflows where the output needs to be normalized JSON instead of browser HTML. ## Google Places API reviews endpoint documentation Use this page as Scrappa's Google Places API reviews endpoint documentation when the official Google Places or Google Business Profile APIs do not return the public Maps review fields your workflow needs. The request path is GET /api/maps/reviews, the required identifier is business_id, and the response is ready for review monitoring, local business enrichment, and reputation analytics pipelines. ## What the reviews endpoint returns Each review item can include review_id, review_text, rating, timestamp, review_updated_timestamp, review_link, review_likes, reviewer identifiers, author profile links, author review counts, Local Guide level, review language, images, owner response text, and owner response timestamps. timestamp is the original review creation time when Google exposes it; review_updated_timestamp is the edited/display timestamp used by Google Maps UI when available. The endpoint keeps every valid review returned by Google Maps and removes duplicate review IDs across fetched pages. First-party reviews have review_source: "Google", a numeric Google contributor author_id, and is_google_review: true. Syndicated reviews remain available with their actual provider, such as Jameda, GoLocal, or Trustpilot, and is_google_review: false; an unknown provider is reported as External. The review_count and reviews_per_rating fields from Google Maps Business Details describe Google's listing totals, but they do not guarantee that every review is available through the paginated public feed. ## Filtering, sorting, localization, and pagination Use search to filter reviews by keyword, sort to request most relevant, newest, highest-rated, or lowest-rated reviews, and page or pages to paginate through larger review sets. A nextPage token is reusable for 30 minutes after it is issued and is valid only for the same business. An invalid or expired token returns a non-billable 410 response with error_code: "continuation_token_invalid_or_expired"; restart from the first page by omitting page. For deeper collection, prefer a multi-page pages request because Scrappa follows continuation tokens inside one request and starts bounded recovery when a full page unexpectedly omits its token. Google can still stop returning a continuation token before the displayed review count is reached, so nextPage: null does not prove that every displayed review was retrievable. Use termination_reason, feed_exhausted, continuation_retries, and continuation_recovered to diagnose how collection stopped. Use hl and gl when your review monitoring workflow needs localized review text, region-specific behavior, or country-specific Google Maps results. ## How to get the business ID before fetching reviews Start with Google Maps Simple Search when you know a business name, category, or address. Use Google Maps Business Details when you need the business profile, rating summary, review count, hours, photos, and place identifiers before calling the reviews endpoint. For one known review, use Single Review.

Fetch photos for a specific business or place with contributor details and pagination support.

Fetch a specific review by its review ID, including full review text, rating, photos, and owner response.

Use the YouTube Channel Videos API when you need a channel upload feed in structured JSON. Send a channel ID and Scrappa returns video IDs, titles, thumbnails, duration, view counts, publish timing, short/live flags, the selected sort order, and pagination metadata. ## YouTube channel uploads API This endpoint is built for developers who need to collect videos from a specific YouTube channel without maintaining browser automation or reverse-engineering YouTube page markup. It fits creator monitoring, competitive content research, media databases, video discovery tools, sponsorship workflows, and analytics jobs that need repeatable channel-level video lists. ## What the channel videos response includes Each response includes a videos array with upload-level fields such as id, title, thumbnail, duration, viewCount, and publishedTime. The pagination object exposes page, pageSize, hasMore, and a continuationToken when more results are available, so you can crawl large channels incrementally instead of relying on a single oversized request. ## Sorting and pagination Use sort=newest for monitoring fresh uploads, sort=popular for finding the channel's top-performing videos, and sort=oldest when you need a historical crawl from the beginning of a channel. Set limit to control page size, then pass the returned continuation token or page through your next request when hasMore is true. ## Related YouTube API workflow Start with YouTube Channel Info when you need the channel name, handle, subscriber count, and profile metadata before collecting uploads. Use YouTube Video Info to enrich individual video IDs, YouTube Comments for audience response, and YouTube Playlist when videos are organized by playlist instead of the channel uploads tab.

Get videos related to a specific YouTube video. Returns up to 20 related videos by default.

Get comprehensive video metadata from YouTube including views, likes, description, and channel info.

Get the transcript for a YouTube video. Also available as /api/youtube/{videoId}/transcript and the matching legacy /api/youtube-external/* aliases.

Scrape public LinkedIn profile information by public URL or numeric member ID, including experience, education, and skills.

Search public LinkedIn job listings using Google Search with an automatic site:linkedin.com/jobs/view/ constraint.

Scrape LinkedIn company page information by public URL or numeric organization ID. Phone and employee growth are null when absent from the public page, even if available in a signed-in view. A missing optional field does not mean the company is unresolved.

Scrape public LinkedIn job posting information including title, company, location, description, and application details.

Search LinkedIn profiles and content via Google. Returns structured results from LinkedIn pages indexed by Google.

Search for companies on Trustpilot by name or keyword. Filters are applied after fetch; pagination counts reflect Trustpilot results.

Search for businesses on Trustpilot with filters. Filters are applied after fetch; pagination counts reflect Trustpilot results.

Get reviews for a company on Trustpilot. Filters are applied after fetch; pagination counts reflect Trustpilot results. Review language defaults to languages=all; pass a 2-letter language code such as languages=de for German reviews.

Search and scrape Google Jobs listings with q, hl/gl, Google domain, uds filters, and pagination options when available. For use cases, free testing, and pricing, see the Google Jobs API overview.

Search Indeed job listings with Scrappa when you need an Indeed API alternative for job search data or a maintained replacement for the deprecated official Indeed Publisher API. Scrappa is not affiliated with or endorsed by Indeed, and this endpoint is not an official Indeed API. It returns structured job listing data as JSON for developer workflows. ## When to use this Indeed jobs API Use this endpoint when you need to search Indeed by keyword, location, country, radius, job type, sort order, and cursor pagination without maintaining a custom Indeed scraper. It is built for job board aggregation, recruiting intelligence, labor market analytics, salary research, and monitoring new postings across cities or countries. Each response includes normalized job listing fields such as title, company, location, salary when available, posting date, apply URL, pagination metadata, and source metadata. That makes it easier to load Indeed results into a database, workflow automation, applicant tracking process, or analytics pipeline. ## How to use Scrappa as an Indeed API alternative The official Indeed Publisher API is deprecated and historically required a publisher relationship. Scrappa provides a direct API-key workflow instead: create a Scrappa account, send a GET request to /api/indeed/jobs, and receive JSON responses that can be processed by your application. Use the authentication docs when adding the x-api-key header, or test the endpoint first in the API playground. ## What the Indeed jobs response returns The endpoint is designed for applications that need records instead of raw search-result HTML. Use query and location for the core search, add country, hl, and gl for localized results, then paginate with cursor when a workflow needs more listings. Store the normalized company, location, salary, apply URL, and pagination fields directly in your job board, recruiting database, saved-search alert, or labor-market analysis pipeline. For broader job search coverage, compare this page with the Google Jobs API documentation, which aggregates job listings from many sources, and the LinkedIn Jobs Search API documentation, which focuses on public LinkedIn job pages. The Indeed Jobs API overview explains use cases, pricing, and related job data endpoints. ## Example workflows - Build a job board that searches Indeed listings by role and location. - Track competitor hiring by monitoring company names and target keywords. - Collect salary ranges and location patterns for compensation research. - Enrich recruiting dashboards with fresh job listing data and apply URLs. - Compare Indeed results with Google Jobs and LinkedIn Jobs coverage.

Fetches a Booking.com search results page and returns structured property cards (name, URL, image, review score, location, price). For best results pass checkin + checkout dates: bare location-only queries on Booking.com redirect to the empty form page.

Accepts a small batch of Booking.com search parameter objects and returns visible price cards for each search. The default server limit is intentionally small to protect the Booking proxy/WAF path.

Fetches a lightweight Booking.com search page and returns the resolved destination URL, destination id, and destination type when Booking exposes them.

Returns visible facility, amenity, and policy text when those sections are rendered in the public hotel page HTML.

Fetches a Booking.com property page and returns structured data extracted from the page (title, canonical URL, JSON-LD Hotel schema, OpenGraph metadata, aggregate rating). Pass either a full Booking.com hotel URL via "url", or a country + slug pair (e.g. country=fr, slug=ritz-paris).

Returns public image URLs exposed through JSON-LD and social metadata on a Booking.com property page.

Returns visible price text from dated Booking.com search result cards. This is a public-page signal, not guaranteed inventory.

Returns paginated public review records exposed through Booking.com review pages. Pass either a full Booking.com hotel URL via "url", or a country + slug pair.

Returns visible room names, prices, occupancy, and bed text when Booking renders room availability for the supplied dates.

Accepts a Booking.com search, city, region, district, landmark, or airport URL and returns the same structured result-card payload as the search endpoint.

Search and filter items on Vinted marketplace. Supports full-text search, category filtering, brand filtering, size/material/status filtering, price range, and sorting options.

Looking for official Vinted API documentation or a public API for item details? Vinted does not provide a generally available public API for developers. Scrappa provides a documented Vinted item details API endpoint that returns listing title, description, photos, pricing, shipping costs, seller profile, item condition, brand, size, category, favorites, and view counts as structured JSON across 19 countries. Use this endpoint when a Vinted search result needs to become a complete product record for resale analytics, price monitoring, catalog enrichment, fraud review, or seller-quality scoring. A typical workflow is to find item IDs with the Vinted Search Items endpoint, enrich each listing with Item Details, compare alternatives with Similar Items, and check delivery context with Item Shipping. Item Details is the enrichment step in a Vinted data workflow. Search results are useful for discovery, but the item details response is where applications can inspect the listing description, gallery, seller reputation, favorites, views, availability, category, localized condition, brand, size, relative upload age, starting shipping price, business status, source URL, and image fields before storing or scoring a product record. Set include_member_items=1 to make an additional upstream request for the seller’s other listing cards. A normal request costs one API request; enabling member items costs two API requests. Successful item responses use listing_status active, sold, hidden, or unavailable. Sold listings return HTTP 200 with availability set to https://schema.org/OutOfStock. A Vinted 404 returns listing_status=not_found because a public request cannot reliably distinguish deletion from a seller-hidden listing. An explicit no-index country shell returns unavailable_in_country. Proxy, blocking, and unparseable upstream pages return listing_status=temporarily_unavailable. Page-derived fields are nullable when Vinted omits them. shipping.from is the displayed starting price, not a guaranteed final delivery cost. upload_date remains Vinted’s localized relative text rather than an inferred timestamp. Always pass the listing country: Vinted may return a reduced page or 404 for an item that is visible in its home market.

Get all available catalog categories with their subcategories. Use the returned catalog IDs with the search endpoint.

Get the supported Vinted countries, TLDs, and currencies. Use this free endpoint to discover valid country values before making paid Vinted API calls.

Get available filter options for a category including brands, sizes, colors, materials, and conditions.

Get items similar to a specific item, typically from the same seller or category.

Get public profile information for a Vinted user including ratings, review count, and items listed.