Website technology stack (tech detection)

GET https://api.api.sh/web/v1/technologies
1 credit / call web data try it in the playground →

The technologies a website runs, detected from its response headers, cookies, meta tags, HTML, script URLs, inline scripts, styles and page elements with an open fingerprint set of thousands of technologies: CMS, e-commerce platform, JavaScript frameworks and libraries, UI frameworks, analytics, tag managers, advertising, marketing automation, live chat, payment processors, CDN, hosting/PaaS, web servers, programming language, databases, security, cookie-consent tools and more. Each item has name, version (where the page shows it), confidence (0-100), categories, website, description, icon, CPE and what it was detected by (implied technologies, such as PHP under WordPress, say implied). Also by_category, the server and x-powered-by headers.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
urlrequired string Public http(s) URL of the page (a bare domain works too). Example: https://wordpress.org/news/
min_confidence integer Only technologies at or above this confidence (0-100). Default: 0
descriptions boolean Include each technology's description. Default true. Default: true
country string Two-letter country to view the page from (default US).

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

Example

curl "https://api.api.sh/web/v1/technologies?url=https%3A%2F%2Fwordpress.org%2Fnews%2F" \
  -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).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.