Lists API

JSON and XML Technology Usage Lists

The BuiltWith Lists API provides XML and JSON access to lists of websites using particular web technologies across the entire internet.

Your Lists API Key -

You are not logged in.

Sign up for Free or Login
You need an active Basic / Pro or Enterprise Plan to use Lists API

Lists API Documentation


The following GET parameters can be supplied for lookups

Name Examples Required
KEY 00000000-0000-0000-0000-000000000000
Sign up for Free or Login to get a key.
The name of a technology, replaces spaces with dashes (-).

T supports multiple technologies seperated by a | character, the first one is the 'base' of your report and will count towards your usage.

AB-Tasty|Magento as a parameter will bring back sites using AB Tasty AND Magento.
META yes
Brings back meta data with the results, which includes names, titles, social links, addresses, emails, telephone numbers, traffic ranks etc.
Gets the next page of results - use the exact value from NextOffset in response. If the value of NextOffset is END there are no more results.
SINCE 2016-01-20
Gets live sites using the technology since a certain time, accepts dates and queries i.e. 30 Days Ago or Last January for example.
FIRSTBETWEEN January 2016 and July 2016
Gets sites using the technology that first started using it between the timeframes. 'and' is required in the parameter but any date formats can be used i.e. 2010-01-1 and last week or last week and today.
LASTBETWEEN January 2012 and December 2012
Gets sites that we last detected using the technology in the past. 'and' is required in the parameter but any date formats can be used i.e. 2010-01-1 and last week or last week and today.
TLD com|uk|au
Only return sites that end with a certain TLD, use | to supply multiple OR queries.
LOCATION Australia
Get results with have a physical address associated with them. Use | to supply multiple OR queries.


The Lists API will send responses in the format -



List2 contains the property of the next page of the report (called NextOffset) as well as the array of Results and potentially an array of Errors.

Name Example Description
NextOffset QWrd7gVNwFQCWb This provides an anchor to the next page of results. Provide this under the request parameter OFFSET to get the next page of results. If NextOffSet is END you are at the end of the list.
Errors Error objects Errors that have occured when trying to do the list lookup.
Results[R] Result objects explain below. All of the results for this lookup.


Results contain R objects that are the websites that match your query.

Name Example Description
D A website that matches the query.
FI 1495580400 Epoch seconds website was first indexed.
LI 1495580400 Epoch seconds website was last indexed.
FD 1495580400 Epoch seconds technology was first detected.
LD 1495580400 Epoch seconds technology was last detected.
Meta Meta object explain below. Supplied when META=yes parameter is used.


Meta data found on the lookup website - detailed lookups only will return meta data if found.

Name Example Description
CompanyName Rodale Inc. A valid incorporated company name
City San Francisco A valid city name for supported countries
Postcode 94105 A valid zip/postal code
State CA A valid state/country
Country US ISO 3166-1 alpha-2 country code for address
Vertical Technology and Computing One of these categories or blank.
[Telephones] +1-650-745-0728 Valid international telephone numbers
[Emails] Valid domain emails
[Social] Social presence
[Names] Name->Joe Bloggs
Names, emails and job titles for people. See titles index for codes


Connection points for the BuiltWith Lists API.

XML Response Endpoint

JSON Response Endpoint

Last database update dates (api.json version)


Example endpoint responses.

All live websites using Optimizely including meta data in XML

Live websites using AB Tasty first detected in the last 30 days in JSON

Live websites using Magento which end in .UK XML

Live websites using Shopify that were first detected between January 2016 and last week in XML

Error Codes

Errors are wrapped as <error>message</error> or [{'error':'message'}] based on request type.

Note error messages in this format cannot be guaranteed, your implementation should also consider non-200 response codes as errors. View all potential well-formed error codes.

Terms and Conditions of Use

Our standard terms cover the use of the BuiltWith Lists API.

In general, you can use the Lists API to enhance your product in many ways. The only limitation is your cannot resell the data as-is or provide duplicate functionality to and its associated services.