Tech Stack Dataset Item API

Endpoint facts

Method

GET

API path

/datasets/techstack/items/{domain}

Auth

apiKey

Credits

1 credit/request

Platform

Datasets

Response schema

#/definitions/datasets.techstackItemResponseDoc

Overview

Returns one site by its domain from dataset id enum value `techstack`, including every detected technology (name, categories, confidence, version, evidence) plus the CMS / e-commerce / CDN / web-server / server-language rollups. Also flags whether the domain looks like backend CDN/DNS/cloud-vendor infrastructure rather than a real, human-navigable site (see `is_infrastructure`). Returns 404 when the domain is not in the index. Developers commonly use this endpoint for repeatable dataset search, filtering, facets, local business enrichment, analytics, exports, and internal tools that need structured records beyond the limited manual refinement available in the Google Maps app. Authentication uses the x-api-key header, usage is metered with the credit cost shown on this page, and the request does not trigger live scraping or proxy routing.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

1 credit/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint reads stored indexed dataset records. It does not execute a live upstream Google Maps request, browser session, or proxy-routed scraping job.

• Data source: stored Crawlora dataset records
• Proxy strategy: no proxy routing is applied
• Browser rendering: not used for dataset search or lookup requests
• Live scraping: not triggered by dataset list, search, nearby, facet, or detail endpoints
• Validation: invalid filters, coordinates, pagination, and enum values return documented errors
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Browser cluster behavior

Some targets require real browser execution because the data is loaded through JavaScript, dynamic rendering, or interaction-like browser behavior.

For supported endpoints, Crawlora can route requests through a managed browser cluster. This allows Crawlora to execute JavaScript, load dynamic content, apply browser-level request behavior, and normalize the rendered result into JSON.

You do not need to operate your own Playwright, Puppeteer, Chrome, proxy, queue, or retry infrastructure.

Response behavior

- The item carries `domain`, `tld`, `rank`, `is_infrastructure` (`true` when the domain looks like backend CDN/DNS/cloud-vendor infrastructure — e.g. `cloudfront.net`, `gtld-servers.net` — rather than a real, human-navigable site; a best-effort heuristic classification, so `false`/absent is not a guarantee the domain is a real site), `reachable`, `status` (HTTP status of the last probe attempt, when one was made), `technologies` (each with `name`, `categories`, `confidence`, `version`, `evidence`), `technology_names`, `categories`, `tech_count`, the `cms`/`ecommerce`/`cdn`/`web_server`/`server_language` rollups, `render_tier`, `detector_version`, and the crawl provenance (`run_id`, `crawled_at`). - When the last probe attempt didn't fully pass, the item also carries `failure_reason` (a short classification, e.g. `"blocked/challenge markers found"`, `"bad status 503"`, `"request failed"`), `probe_error` (the first line of the underlying transport error, when there was one), and `block_matched` (which block/challenge marker(s) were found, when `failure_reason` is a block/challenge classification). This can appear even when `reachable` is `true` — a blocked page returning a non-5xx status still counts as reachable while carrying a failure reason. Absent for a site that fully passed. - When the crawl looked for extra non-homepage pages (opt-in per run), the item also carries `secondary_pages_discovered` (count of candidate pages found on the homepage nav, regardless of fetch outcome), `secondary_pages_fetched` (count that were actually fetched successfully and contributed content — always <= discovered), `secondary_page_categories` (which categories were successfully fetched and contributed, e.g. `login`, `docs`, `cart`), `secondary_pages` (the full per-page audit trail — every discovered candidate, each entry `{category, url, fetched}`; `fetched: false` means the candidate was found on the homepage nav but the fetch itself failed, e.g. blocked or timed out), and `secondary_only_technology_names` (technology names detected only via a fetched secondary page, not the homepage itself — a subset of `technology_names`). Absent when no secondary pages were discovered for that run. - Returns the standard not-found envelope when the domain is not in the index. - Does not trigger live scraping; for a live, on-demand fingerprint of any URL use `/web/techstack`. Example response: ```json { "code": 200, "msg": "OK", "data": { "domain": "example-store.com", "tld": "com", "rank": 5231, "reachable": true, "technologies": [ { "name": "Shopify", "categories": ["Ecommerce"], "confidence": "high", "evidence": "markup: cdn.shopify.com" }, { "name": "Google Analytics", "categories": ["Analytics"], "confidence": "high", "evidence": "script: googletagmanager.com/gtag/js" }, { "name": "Cloudflare", "categories": ["CDN"], "confidence": "high", "evidence": "header: cf-ray" } ], "technology_names": ["Shopify", "Google Analytics", "Cloudflare", "Afterpay"], "categories": ["Analytics", "CDN", "Ecommerce", "Payment"], "tech_count": 4, "ecommerce": "Shopify", "cdn": "Cloudflare", "secondary_pages_discovered": 2, "secondary_pages_fetched": 1, "secondary_page_categories": ["cart"], "secondary_pages": [ { "category": "cart", "url": "https://example-store.com/cart", "fetched": true }, { "category": "docs", "url": "https://example-store.com/docs", "fetched": false } ], "secondary_only_technology_names": ["Afterpay"], "render_tier": "http", "detector_version": "2026.07.4", "run_id": "top1m-2026-07-08" } } ```

Error behavior

Crawlora does not silently return invalid dataset search results when filters, pagination, coordinates, or stored record lookups cannot be satisfied.

When possible, Crawlora returns structured error context so your integration can adjust filters, page size, location inputs, or lookup identifiers.

Related