/wappalyzer/technologies

POST /api/wappalyzer/technologies

Price: 1 credit

Get a Wappalyzer technology profile by slug — usage, market share, geography and alternatives

How to use it

Look up a web technology on Wappalyzer by its slug (e.g. 'shopify', 'react') or profile URL. Returns the technology's name, description, official website, pricing model, whether it is SaaS / open-source / versioned, the total number of live websites tracked, the categories it belongs to, the breakdown of top countries and languages where it is used, a sample of top websites using it (hostname, traffic level, tech spend, country), and the top alternative technologies. Useful for technographics, market research and competitive analysis.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• technology string required — Technology slug or its Wappalyzer profile URL (examples: "shopify", "react", "https://www.wappalyzer.com/technologies/ecommerce/shopify/"; minLength: 1)

Response

• @type string (default: "WappalyzerTechnology")
• alias string required
• name string nullable
• image string nullable
• website_url string nullable
• description string nullable
• pricing array (default: [])
• is_saas boolean nullable
• is_oss boolean nullable
• is_versioned boolean nullable
• website_count integer nullable
• created_at integer nullable
• categories array (default: [])
  • @type string (default: "WappalyzerTechnologyCategory")
  • id integer nullable
  • alias string required
  • name string nullable
  • priority integer nullable
• top_countries array (default: [])
  • @type string (default: "WappalyzerCountryStat")
  • country string required
  • count integer required
• top_languages array (default: [])
  • @type string (default: "WappalyzerLanguageStat")
  • language string required
  • count integer required
• top_websites array (default: [])
  • @type string (default: "WappalyzerTopWebsite")
  • hostname string required
  • traffic_level string nullable
  • tech_spend string nullable
  • country string nullable
• alternatives array (default: [])
  • @type string (default: "WappalyzerAlternative")
  • alias string required
  • name string nullable
  • image string nullable
  • category string nullable
  • category_alias string nullable
  • hit_count integer nullable
  • website_count integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Technology not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.