/wappalyzer/categories

POST /api/wappalyzer/categories

Price: 5 credits

Get a Wappalyzer technology category with its market-share ranking of technologies

How to use it

Look up a Wappalyzer technology category by its slug (e.g. 'ecommerce', 'javascript-frameworks') or category URL. Returns the category name, its parent groups, and the full ranking of technologies in that category by market share — each with the number of live websites tracked, total detections, and its market-share percentage within the category. Useful for market research and finding the leading technologies in a segment.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• category string required — Category slug or its Wappalyzer category URL (examples: "ecommerce", "javascript-frameworks", "https://www.wappalyzer.com/technologies/ecommerce/"; minLength: 1)

Response

• @type string (default: "WappalyzerCategory")
• id integer nullable
• alias string required
• name string nullable
• priority integer nullable
• technology_count integer nullable
• created_at integer nullable
• updated_at integer nullable
• groups array (default: [])
  • @type string (default: "WappalyzerCategoryGroup")
  • id integer nullable
  • alias string required
  • name string nullable
• technologies array (default: [])
  • @type string (default: "WappalyzerCategoryTechnology")
  • alias string required
  • name string nullable
  • image string nullable
  • hit_count integer nullable
  • website_count integer nullable
  • market_share number 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 — Category 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.