Wappalyzer · Controlled Vocabulary
Wappalyzer API Vocabulary
Canonical terms and definitions used across the Wappalyzer technology detection API.
18 Terms
Updated
Wappalyzer Vocabulary is a controlled vocabulary published by Wappalyzer on the APIs.io network, defining 18 terms.
Defined terms include technology, category, lookup, crawl, and credit.
A controlled vocabulary pins the words an API’s schemas, parameters and documentation use to one agreed definition each — the shared language a human or an agent needs to read the API the same way its authors do.
Terms
technology
A software component, framework, CMS, analytics tool, or platform identified as being used on a website. Each technology carries a slug, human-readable name, optional CPE identifier, detected version strings, and one or more category classifications.
category
A classification grouping for technologies (e.g. CMS, Ecommerce, Analytics). A technology may belong to multiple categories.
lookup
The act of querying Wappalyzer to identify all technologies used on one or more websites. Lookups may return cached results or initiate a live or recursive crawl. Results may arrive synchronously or asynchronously via a callback URL.
crawl
An asynchronous multi-page scan of a website initiated when recursive=true and no cached result is available. The caller receives a pending marker in the synchronous response and the final result via callback.
credit
The unit of billing consumed by Wappalyzer API calls. Each technology detection, lead list row, subdomain record, or email verification consumes a defined number of credits. Balance is returned in the wappalyzer-credits-remaining response header.
lead_list
A filtered, exportable dataset of websites identified as using specific technologies. Created via POST /v2/lists, priced asynchronously, and finalized by spending credits. Available in JSON or CSV format.
list_status
The lifecycle state of a lead list. One of: Calculating (being priced), Ready (priced and awaiting finalization), Failed (could not be generated), Insufficient (insufficient matching websites), Complete (finalized and downloadable).
subdomain
A hostname that is a child of a queried domain and is confirmed to serve web content. Returned by GET /v2/subdomains with pagination support via the moreAfter cursor.
email_verification
A multi-check assessment of an email address covering syntax validity, MX record existence, SMTP connection, deliverability, disposability, and role-account classification. Returned by GET /v2/verify.
reachable
The overall deliverability verdict for an email address. One of: safe (deliverable with high confidence), risky (may bounce), invalid (will not deliver), unknown (could not determine).
technology_spend
An estimated relative spend on technology stack inferred from the detected technologies. Reported as a qualitative band.
traffic_level
A relative classification of a website's monthly traffic volume based on Wappalyzer's data. Reported as a qualitative band when the signals set is requested.
sets
Optional named result field sets that can be requested to include additional data in lookup or list responses. The `signals` set adds technologySpend and trafficLevel fields.
denoise
A query parameter that, when true (the default), excludes low-confidence technology detections from lookup results.
squash
A query parameter that, when true (the default), merges monthly cached result sets into a single consolidated result.
callback_url
A publicly reachable HTTPS endpoint provided by the API caller. Wappalyzer POSTs asynchronous results (crawl completions, list ready notifications) to this URL, optionally including a wappalyzer-signature header for verification.
wappalyzer_signature
An HMAC signature header included in asynchronous callback POST requests from Wappalyzer, allowing the recipient to verify the payload originated from Wappalyzer.
x_api_key
The API authentication header required for all Wappalyzer API requests. Keys are available from the Wappalyzer dashboard.
Controlled Vocabulary
Work with this as data
Every vocabulary here is available over the APIs.io API and to AI agents over MCP. Vocabularies is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.