Basics
A Business plan is required to use this feature.
Wappalyzer APIs give your product, sales, and data workflows access to website, company, and email intelligence. Use them to enrich CRM records, qualify accounts, build lead lists, verify email addresses, and analyze websites in real time.
Across the API docs, every endpoint…
- Conform to REST principles
- Return JSON data
- Require authentication
- Are metered and rate-limited
- Are HTTPS only
API calls consume credits so you can scale usage across lookups, lead lists, and verification workflows. Credits are included in selected plans, and you can purchase more whenever you need additional volume.
Authenticate requests with an API key. Create one in your account and
use it in the x-api-key header for server-side jobs,
internal tools, and production integrations.
| Request header | Value |
|---|---|
x-api-key | Your API key |
Download the OpenAPI 3.1 contract for Wappalyzer's documented public REST endpoints. Use it to import the API into Postman or Insomnia, generate a client, or validate callback-aware integrations against a machine-readable schema.
The published spec is available at
/openapi/v2-public.yaml.
If you use callbacks for async lookups or list generation, sign those requests so your application can trust incoming payloads. To enable signing, create a signing secret.
To verify a callback, create a SHA256 hash of the signing secret
appended with the raw JSON request body. The request is valid if the
hash matches the value in the wappalyzer-signature header.
sha256(secret + body) == signature
| Request header | Value |
|---|---|
wappalyzer-signature | SHA256 hash |
Every response includes a standard HTTP status code alongside the JSON body so your application can decide whether to continue, retry, or surface an error.
| HTTP code | Description |
|---|---|
200 | The request was completed successfully |
400 | There was an error with the request |
403 | Authorization failure (incorrect API key, invalid method or resource or insufficient credits) |
429 | Rate limit exceeded |
2xx response as success, 4xx as a request or
account issue to fix, and 5xx as a temporary server-side
failure.
Every successful response includes headers for credits spent and credits remaining, so you can monitor usage and avoid interrupting automated jobs.
| Header | Description |
|---|---|
wappalyzer-credits-spent | The number of credits deducted |
wappalyzer-credits-remaining | Your credit balance |
If you want to check balance before starting a job, call the dedicated credits endpoint:
GET https://api.wappalyzer.com/v2/credits/balance/
Request
curl -H "x-api-key: <your api key>" "https://api.wappalyzer.com/v2/credits/balance/"
Response
{ "credits": 100000 }
Subscribe to receive occasional product updates.