Scrappa API docs and endpoint search

Perform a Google search and get structured results including organic results, related searches, knowledge graphs, and more.

Fetch a modern Google SERP through the browser orchestrator 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.

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".

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 reviews summary.

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_link, review_likes, reviewer identifiers, author profile links, author review counts, Local Guide level, review language, images, owner response text, and owner response timestamps. The response also includes nextPage when more reviews are available. ## 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. 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.

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

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 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, condition, brand, size, total item price, shipping price, service fee, source URL, and image fields before storing or scoring a product record.

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.

Fetch the detailed Arbeitsagentur job payload for a single listing, including the full description, employer website, and contact details when the upstream source provides them.

Search job listings from Germany's Federal Employment Agency with powerful filters. Supports filtering by keyword (was), location (wo), search radius (umkreis), offer type (angebotsart), working hours (arbeitszeit), publication date (veroeffentlichtseit), occupational field (berufsfeld), employer (arbeitgeber), contract type (befristung), temporary work (zeitarbeit), and pagination (page, size).

Search for valid German location identifiers used as input for the Job Search endpoint. Look up locations by postal code (plz) or search term (suchwort) to obtain structured location data.

Check a domain against the authoritative RDAP server listed in the IANA bootstrap registry. RDAP can identify registered domains and can indicate that a domain is probably available when the registry returns not found. Registrar checkout availability, premium pricing, aftermarket inventory, reserved names, and registration restrictions require registrar or registry availability data.

Use the Google Finance quote API when you need a single ticker-level response for a stock, ETF, or other Google Finance instrument. The endpoint returns current price fields, market status, previous close, day range, year range, market cap, P/E ratio, dividend yield, company profile details, financial statement rows, related news, and discovery tickers as structured JSON. This page is built for developers comparing stock quote APIs, finance quote JSON endpoints, and Google Finance data extraction workflows. Start with Search Financial Instruments when you only know a company name, then call this quote endpoint with the resolved symbol and exchange. Pair quote data with Historical Data for backtests, Intraday Graph Data for charting, and Markets Overview for broader market context.

Get historical price and volume data for a financial instrument. Supports various time ranges from 1 day to maximum available, or custom date ranges with configurable intervals. Pair this with the Google Finance quote API when you need current price, company details, key statistics, financials, and news for the same ticker.

Get intraday minute-by-minute price and volume data for a stock from Google Finance. Returns data points with price, volume, and formatted timestamps. Use the Google Finance quote API alongside intraday charts when you also need quote summary fields, key statistics, company information, financials, and news.

Get real-time data for major market indices including S&P 500, Dow Jones, NASDAQ, and Russell 2000. For individual stock detail after checking market benchmarks, use the Google Finance quote API.

Get a comprehensive overview of global financial markets from Google Finance. Without the trend parameter, returns a summary of US, European, and Asian market indices, currencies, cryptocurrencies, and futures. With the trend parameter, returns detailed market trend data (gainers, losers, most active, indexes, climate leaders, cryptocurrencies, currencies) including market_trends and news_results. When a market mover needs deeper ticker-level data, open the Google Finance quote API.

Search for financial instruments by name, symbol, or keyword. Returns matching stocks, ETFs, cryptocurrencies, and other tradable assets. After resolving the symbol and exchange, use the Google Finance quote API to fetch the complete stock profile, key stats, financials, and news.

Returns a list of supported airlines with their IATA codes and names. Free endpoint.

Returns a list of major airports with IATA codes, names, and locations. Free endpoint.

Get detailed booking information for a specific flight including price insights, price history, fare options, and baggage information.

Search across a date range to find the cheapest flight dates. Returns price data for each date combination.

Search for one-way flights between airports. Returns flight options with prices, durations, airlines, and layover information.

Search for round-trip flights. Includes outbound and return flight options with combined pricing.

The Google Hotels Autocomplete API provides real-time location and hotel name suggestions as users type, powered by the same suggestion engine behind Google Hotels. Build type-ahead search experiences for travel apps, hotel booking platforms, and destination discovery tools.What You GetHotel suggestions — Specific accommodations matching the query (e.g., "Paris Hotel Las Vegas", "Hilton London Bankside")Location suggestions — Cities, regions, and landmarks (e.g., "Paris, France", "Times Square, New York")Direct booking links — Each suggestion includes a ready-to-use scrappa_google_hotels_link to fetch full hotel search resultsThumbnails & metadata — Hotel images, Knowledge Graph IDs (kgmid), and property tokens for deeper lookupsCommon Use CasesTravel search bars — Power autocomplete dropdowns in hotel booking interfaces with instant suggestionsDestination discovery — Help users explore locations by surfacing relevant cities and landmarks as they typeHotel name resolution — Resolve partial hotel names to exact properties with unique identifiers and property tokensMulti-language support — Localize suggestions for 50+ languages using the hl and gl parametersHow It WorksSend a partial query (minimum 2 characters) and the API returns ranked suggestions from Google's hotel database. Use the type parameter to filter results:hotel (default) — Returns only accommodation suggestions (specific hotels, resorts, hostels)location — Returns only geographic suggestions (cities, regions, landmarks)all — Returns both hotel and location suggestions togetherResponse Type ValuesEach suggestion includes a type field indicating the suggestion category:accommodation — Hotels, resorts, hostels, and other lodging propertieslocation — Cities, regions, landmarks, and geographic areasEach suggestion includes a scrappa_google_hotels_link that you can call directly to get full hotel search results for that location or property — no extra parameter mapping needed.Scrappa vs. Building Your OwnGoogle does not offer a public Hotels Autocomplete API. Building this yourself requires reverse-engineering Google's internal batchexecute protocol, handling protobuf-encoded payloads, and maintaining parsers as Google changes their internal format. Scrappa handles all of this, returning clean JSON with a simple REST interface.

Search for hotels by location with comprehensive filtering options. Supports price range, star rating, free cancellation, and sorting options. Use the Google Hotels Autocomplete endpoint to get valid location suggestions and property tokens for this endpoint.

Search and scrape image results from Google Images with advanced filtering by size, type, color, and aspect ratio. Returns structured data including thumbnail URLs, full-resolution original image URLs, source attribution, and image dimensions for each result. ### Key Features - Image metadata extraction — Get titles, source websites, thumbnails, and original high-resolution image URLs in a single request - Advanced filtering — Filter results by image size (large, medium, icon), type (photo, clipart, lineart, gif, face), dominant color (14 options), and aspect ratio (tall, square, wide) - Localization support — Target results by language (hl) and country (gl) for region-specific image search - Pagination — Retrieve multiple pages of results to access hundreds of images per query - Time-based filtering — Use the tbs parameter to find images from the past day, week, month, or year - Safe search — Enable or disable explicit content filtering for content-appropriate results ### Common Use Cases - E-commerce product research — Gather product images and visual competitive intelligence across marketplaces - Content creation and curation — Find reference images, stock photos, and visual assets for blogs, presentations, and marketing materials - Brand monitoring — Track where brand logos and product images appear across the web - Visual dataset collection — Build image datasets for machine learning training, computer vision projects, and AI model development - SEO and visual search analysis — Monitor which images rank for specific queries and analyze visual SERP features - Market trend analysis — Identify trending visual styles, design patterns, and popular imagery in any niche

Search for patents on Google Patents. Supports filtering by date, country, language, patent status, and more.

Get autocomplete suggestions for a search query. Useful for discovering trending searches and related keywords.

Retrieve historical interest data for a keyword over a specified time period. Returns a timeline of interest values (0-100) showing search popularity trends.

Retrieve queries and topics related to your search term. Shows what else people search for in relation to your keyword.

Search for locations (cities, districts, postal codes) and get geocodes that can be used in property search.

Get average price per square meter for a location. Returns rental and purchase prices for apartments and houses.

Get detailed information about a specific property listing including price breakdown, features, images, energy class, and agent contact.

Search for real estate listings on Immobilienscout24 with filters for location, property type, price range, rooms, and size.

Scrappa's GET /api/immowelt/search endpoint is the Immowelt Search API documentation page for developers who need Immowelt.de property listings as structured JSON instead of building their own scraper. ## Endpoint reference for Immowelt.de property search Use this endpoint to search apartments and houses for rent or sale across Germany. The request supports location, listing type, price ranges, room filters, size filters, page, and per_page, which makes it suitable for search interfaces, market monitoring, lead generation, rental alerting systems, and German real estate data products that need repeatable result feeds. ## What the Immowelt search response returns Each response includes listing IDs, online IDs, listing titles, prices, room counts, square meter values, address text, coordinates, image URLs, listing URLs, publish timestamps, and pagination fields such as total_results, page, and total_pages. That gives you a search-ready listing feed instead of raw HTML that still needs parsing. ## How this differs from an Immowelt scraper build If you are evaluating how to scrape Immowelt.de, this endpoint replaces the brittle search step with one documented API call. Scrappa handles request routing, extraction, and normalization so your application can focus on query logic and downstream analysis rather than browser automation, proxy rotation, or parser upkeep. ## Immowelt search API use cases Use the search endpoint as the first step in workflows that need fresh German property supply data. Rental analytics teams can query Berlin, Munich, Hamburg, Cologne, and Frankfurt with consistent room, size, and price filters to compare availability by city or district. Proptech products can run saved searches for renters and buyers, then trigger alerts when new listings match a budget, room count, or square meter range. Real estate investors can combine paginated search results with listing details to screen neighborhoods, compare yield assumptions, and monitor asking-price changes over time. For cross-portal coverage, query Immowelt search beside ImmobilienScout24 or other real estate APIs and deduplicate by address, coordinates, listing URL, and price. This gives applications a broader view of the German housing market than a single portal search page can provide. ## When to pair this endpoint with the other Immowelt docs Use Location Autocomplete to resolve cities, districts, and postal codes before search. Use Search Count when you want to estimate market size before paginating through result sets. Use Property Details when a search result needs to be enriched into a single listing record. For broader German real estate coverage, compare the Immowelt API overview and the Immobilienscout24 Search API.

Search for locations and get IDs that can be passed back into /immowelt/search as the location parameter. Returns coordinate-based suggestions via geocoding, plus optional placeId enrichment.

Fetch property details from Scrappa cache populated by the last /immowelt/search call. This avoids calling expose/detail endpoints that may be WAF/DataDome-blocked.

Get total listing count for a placeId + distribution + estateType using Immowelt BFF.

Retrieve detailed information about a specific Instagram post by URL. For best results, use URLs that include the username (e.g., instagram.com/username/p/ABC123/). URLs without username (e.g., instagram.com/p/ABC123/) will attempt automatic username discovery, but this may not always succeed. Returns media URLs, captions, engagement metrics, author info, and tagged users.

Retrieve Instagram profile API data including biography, bio links, follower/following counts, and profile picture. Use the separate /user/posts endpoint to fetch the user's posts. Instagram may reject some platform-owned or restricted profiles upstream, including @instagram, so use a public profile username for test requests.

Retrieve an Instagram user's posts with pagination support. Returns post details including media URLs, captions, engagement metrics, and a pagination cursor for fetching more posts.

Get detailed doctor information, reviews, and ratings from Jameda. The doctor_url parameter accepts multiple formats: full URL (https://www.jameda.de/dr-name/specialty/city), path with leading slash (/dr-name/specialty/city), or path without leading slash (dr-name/specialty/city). All formats are normalized internally.

Get patient reviews and ratings from Jameda. The doctor_url parameter accepts individual doctor profile URLs, plus provider/facility pages under /gesundheitseinrichtungen. Facility URLs with a filters[doctor_id] fragment use the selected doctor review feed; facility URLs without a selected doctor ID return the reviews available on the profile page.

Get autocomplete suggestions for locations. Both "q" and "query" parameters are accepted for backward compatibility, but "q" is preferred.

Search for doctors on Jameda by specialty or doctor name with optional location.

Get autocomplete suggestions for medical services and specialties. Both "q" and "query" parameters are accepted for backward compatibility, but "q" is preferred.

Fetch a public Kununu job posting and return the full description, structured contact information, and page metadata when they are available on the listing.

Search and filter job listings on Kununu with support for location, workplace model, employment type, career level, industry, discipline, benefits, and more.

Search Kununu companies by brand name, employer keyword, or industry category and return structured employer profile matches from the DACH region. Use the Kununu Search API to discover company review profiles before fetching deeper employer data such as employee reviews, profile details, ratings, locations, industries, benefits, and open job counts. Filter results by country or industry to build HR tech products, employer reputation dashboards, competitive research workflows, and company-review datasets.

Get Redfin automated home valuation data for a specific US property. The endpoint is designed for AVM-style workflows where you already have a Redfin property_id from search results or a property details lookup and need a structured estimate, low/high value range, last sale context, and comparable-property signals. What the Redfin valuation endpoint returns The response can include the predicted home value, estimated low and high bounds, last sold price, last sold date, beds, baths, square footage, lot size, year built, and comparable sales. These fields are useful for building home equity calculators, pricing research tools, investment screening dashboards, portfolio monitoring, and homeowner-facing value estimate experiences. How to get a property valuation Start with Redfin Location Search when you need region IDs, then use Redfin Property Search to find candidate listings and extract the property_id. For a known property, call Redfin Property Details first when you need richer listing context before requesting this valuation endpoint. When to use valuation instead of property search Use property search when you need a list of homes in a city, ZIP code, county, or neighborhood. Use Redfin Home Valuation when your workflow centers on one property and needs an estimated value range, comparable sales, and property attributes for underwriting, pricing analysis, or automated real estate reports.

Search for locations (cities, ZIP codes, neighborhoods) and get region IDs for use with the search endpoint.

Search for real estate listings on Redfin using a region_id, region_type, and market from the locations endpoint.

Startpage API documentation for developers who need Startpage search results in JSON. Scrappa's GET /api/startpage/search endpoint returns anonymous Startpage web results with titles, descriptions, URLs, domains, and pagination metadata. ## Startpage API for search results Use this Startpage API endpoint when you want Startpage results in an API response instead of maintaining your own scraper. It fits SERP monitoring, privacy-first search products, research pipelines, rank tracking, compliance review tools, and automation workflows that need anonymous web search data. ## What you get from the Startpage API Each response includes ranked organic results with position, title, description, url, and domain, plus total_results and source. You can use language, page, and safe_search to request localized or filtered Startpage result sets for privacy-focused search products, SEO analysis, and market research. ## How to call the Startpage Search API Send a GET request to /api/startpage/search with a required query parameter and your Scrappa API key in the x-api-key header. Add language=english, page=0, and safe_search=true when you need reproducible first-page results for monitoring, testing, or customer-facing search features. ## Startpage response fields for developers Use position to preserve ranking order, title and description for result previews, url for destination links, and domain for grouping or deduplication. The source field identifies the response as startpage, which helps when you combine this endpoint with Google Search or other Scrappa search APIs in the same pipeline. ## When to use Startpage instead of other search APIs Choose this endpoint when you need Google-quality results through a privacy proxy and do not want user-level personalization or tracking signals affecting the result set. That makes it useful for neutral SERP monitoring, compliance-sensitive products, and teams comparing multiple search engines from one Scrappa account. ## Implementation and indexing notes The Startpage Search API is a REST endpoint, so it works with backend jobs, browser-based admin tools, AI agents, and scheduled rank-tracking workflows. For authentication details, see the API authentication guide. To test a request in the browser before writing code, open the API playground or compare usage against the pay-as-you-go scraping API guide. ## Related search workflow docs Use Google Search API when you need Google web results. For a broader overview of pricing, positioning, and usage, see the Startpage API overview.

Get autocomplete suggestions for job search queries. Returns matching job sectors and locations from Stepstone.

Search job listings on Stepstone with keyword, location, and filter support. Covers Germany (de), Austria (at), Netherlands (nl), and Belgium (be).

Discover users related to a TikTok account by unique ID or user ID.

Fetch TikTok follower lists as structured JSON for audience research, influencer discovery, creator vetting, and social graph analysis. Use a username or numeric user ID to inspect who follows a public TikTok account, page through follower data, and enrich creator intelligence workflows.

Use Scrappa's TikTok user search API to find public TikTok accounts by username, brand name, creator niche, product category, or keyword. The GET /api/tiktok/user/search endpoint returns matching user records as structured JSON with cursor-based pagination, so developer teams can build creator discovery, influencer research, social listening, and profile enrichment workflows without maintaining a TikTok search scraper. ## TikTok user search API for creator discovery Search keywords such as a creator niche, brand term, campaign phrase, location, product category, or username fragment to discover public TikTok accounts. This endpoint is useful when you need a TikTok username search API for influencer databases, creator marketplaces, social CRM enrichment, competitor account discovery, or brand safety review queues. ## What the TikTok user search response returns The response includes a users array with account identifiers and profile fields such as user_id, unique_id, nickname, avatar, follower_count, and verified when the upstream returns them. Use unique_id as the human-readable TikTok handle, user_id as the stable account identifier for follow-up API calls, follower_count for audience-size filtering, and verified to separate official or notable accounts from lookalikes. ## How to call the TikTok User Search API Send a GET request to /api/tiktok/user/search with the required keywords parameter and your Scrappa API key in the x-api-key header. Add count to control page size and pass the returned cursor into the next request when hasMore is true. ## Common TikTok user search workflows Start with this endpoint when you need a seed list of accounts, then enrich or analyze those users with adjacent TikTok endpoints. Discover creators by niche, fetch profile details with the TikTok User Profile API, review recent videos with the TikTok User Posts API, inspect follower or following graphs with TikTok Followers API, or compare account discovery against keyword video search through the TikTok Feed Search API. ## Related TikTok API docs For the full endpoint family, pricing context, and TikTok API use cases, see the TikTok API overview. For authentication details, use the API authentication guide. To test a request before writing code, open the API playground.

Resolve a TikTok video, photo post, short URL, or raw video ID into metadata and playback URLs from the configured RapidAPI upstream.

Fetch public TikTok posts for a user by unique ID or user ID.

Fetch TikTok story data for a user by unique ID or user ID.

Get available TrustedShops shop categories for a specific market and return category names, IDs, total shop counts, and URL path values as structured JSON. Use TrustedShops Markets to choose a supported country code first. Then pass a returned urlPath value to TrustedShops Category Shops to browse shops inside that category.

Browse shops within a TrustedShops category and market, then return paginated merchant profiles with TSIDs, names, ratings, review counts, certification state, categories, and profile URLs. Use TrustedShops Categories first to get valid category urlPath values for a market. Use TrustedShops Shop Profile or TrustedShops Reviews when you want to enrich or monitor shops returned by this category browsing endpoint.

List every TrustedShops market supported by Scrappa and return the country names plus ISO alpha-3 market codes required by market-aware endpoints. This free metadata endpoint helps you choose valid country filters before running shop search, category discovery, or category browsing requests. Use TrustedShops Search when you already know a shop or brand name. Use TrustedShops Categories to fetch category URL paths for a market, then call TrustedShops Category Shops to page through shops in that category.

Fetch review records for a specific TrustedShops shop by TSID and return structured review data for reputation monitoring, product quality analysis, review dashboards, and merchant intelligence workflows. Use TrustedShops Search to find the TSID for a shop name or domain first. Call TrustedShops Shop Profile when you need profile metadata for the same merchant, including its target market and profile-level fields.

Search TrustedShops shop profiles by brand name, domain, or merchant keyword and return matching European e-commerce shops as structured JSON. Each result can include the shop name, TSID, TrustedShops profile URL, rating summary, review count, category assignments, certification state, and market-specific metadata. Use this endpoint when you need to resolve a human search term into TrustedShops identifiers before calling TrustedShops Shop Profile or TrustedShops Reviews. Pair search with TrustedShops Markets to choose the right country code and TrustedShops Categories when building category-level shop discovery workflows.

Fetch a single TrustedShops shop profile by TSID and return merchant-level profile data as structured JSON. The response is useful when you need to enrich a known TrustedShops ID with the shop URL, display name, language, target market, and profile metadata before joining it to reviews or search results. Start with TrustedShops Search if you need to discover the TSID from a shop name or domain. Use TrustedShops Reviews for review-level records from the same TSID, or TrustedShops Markets to validate the market codes used across the TrustedShops docs cluster.

Dynamically extracts specified fields from a domain's impressum page. Uses Brave Search to find the impressum, fetches the page, and uses AI to extract the requested fields.

Fetch any URL and extract structured data including title, meta description, keywords, favicon, social links, all links on the page, emails, phone numbers, images, body text, and detected languages. Returns the site's HTTP status code separately so you can distinguish site errors (404, 500) from infrastructure errors. Use response_type=markdown to get only the page content as clean markdown.

Search for B2B suppliers, products, and services on wlw.de (Wer liefert was). Supports filtering by country, category, employee count, supplier type, location, price range, and more.