Technology Stack

FREEMIUM
By findmassleads | Updated 15 days ago | Business Software
Popularity

7.6 / 10

Latency

618ms

Service Level

100%

Health Check

N/A

README

You have access to 3 endpoints. You get technology data as well as email information for almost every domain in the world.
We are a big data startup and we help small companies discover untapped mines of leads from the technologies they use.

How to use these email addresses then?
You can use a very affordable tool like lemlist, mailshake, quickmail… to automate a cold outreach campaign.
Don’t sell on first email. You want to engage conversation. And get new clients fast!

We’re listening to your feedback! Feel free to email us at support@findmassleads.com. We’ll be happy to help 😃

**============================**
1 - Technology Information endpoint

description:
Returns an object. Each key is a technology id. Values are technology category and name.
We suggest that, at the beginning of your program, you load this full technology information object once for later use in your code.
Thus, from a technology numerical ID, you can easily get the technology category and name.

You can save it in a file if you want for future use. But be aware that we add more and more technologies all the time. Names and categories may change. On the contrary, technology ids will stay the same.

route: /RAPItif9m11S3g5f/

method: POST

parameters: none

result:
{
“100”:{
“CATEGORY”:“Analytics”
“FULLNAME”:“Google Analytics”
“NAME”:“googleanalytics_”
},
“101”:{
“CATEGORY”:“Survey”
“FULLNAME”:“Apester”
“NAME”:“apester_________”
},
“102”:{
“CATEGORY”:“Automation”
… and so on.

Explanations: “100” is the technology id. “FULLNAME” is the human name. “NAME” is the 16-char lower case no space name.

You will need technology ids to get the technology names and to perform lead searches later.
That’s why we recommend you load this endpoint once.

**======================**
2 - Domain Lookup endpoint

description:
Returns an object. From a domain name, you get the URLs with language, technologies used, ranking, estimate of tech spend, email addresses, favicon url, phone numbers, social links.

route: /RAPIdnR9519Saggh/

method: POST

parameters: JSON
dn: Domain name without http(s)😕/ nor any slash.
example: {“dn”:“tesla.com”}

result:
Example:
{
“6”:{…}
“7”:{
“uri_count”:122
"https%3A%2F%2Fbravebrownbag.com%2Fblogs%2Fnews%2F14456549-aero-studios-beauty-of-the-practical-and-useful":{
“lang”:“en”
“f _ids”:{
“OXq”:true
}
“i _ids”:{
“5mA”:true
}
“tech _ids”:{
“115”:true
"312":true
"339":true
"384":true
"575":true
}
}
“pagerank _pos”:8078878
"favicon _url":"%2F%2Fcdn2.shopify.com%2Fs%2Ffiles%2F1%2F0184%2F8190%2Ft%2F10%2Fassets%2Ffavicon.png%3F297"
… and so on.

Explanations on how to read that:
The result is an object.
“6” and “7” are two consecutive month indices (June 2019 and July 2019 in this case). These indices start at year 2019. So, for example, January 2019 is 1, December 2019 is 12. January 2020 is 13. March 2021 is 27.
Right now, you get data from current month index -2 and -3. So let’s say we’re in Dec 2019, you’ll get data from September and October (9 and 10). We work on reducing that delay.

The values are object with URLs as keys (use javascript function decodeUriComponent to decode the URLs), and values are the following objects:
“lang” is the language of the page (supported: en, sp, po, fr, de, da, nl, it)
"* _ids" are the contact ids. * can be “e” (email address), “t” (phone number), “f” (Facebook), “k” (LinkedIn), “i” (Instagram), “w” (Twitter) and “y” (YouTube).
"“tech _ids”" are the technology ids. Use the first endpoint to get the technology names.
“pagerank _pos”, its’ actually not a rank for this page (url) but for the whole domain.
“favicon _url” is the path to the favicon of the website we’ve detected on this page. It may exist in many pages.

The other main keys:
“contacts”: the keys are the contacts. Use javascript function decodeUriComponent to decode. It can be an email address, a phone number, a facebook page… etc.
Note that their “id” is the one that the pages which have contact information refer to just above. See the “* _ ids” objects.
“contact _ count” is the number of unique contacts we’ve detected on all the pages above.
“location” is probably empty. We do not provide the location most of the time.
“all_ unique_ tech_ ids” is the summary of all the technology ids we’ve detected on all the URLs above. Use the first endpoint to get the technology names.
“langs” is the summary of all the languages and their count we’ve detected on all the URLs above.
“total_ monthly_ tech_ spent” is an estimation of the overall monthly tech spend in USD for this domain.
“pagerank _ pos_ relative_ pct” is a percentage. 100 correspond the top ranked domains. 90 is a high ranked one. 10 is a poorly ranked domain.
“pagerank _ pos_ value” is the actual Page Rank of the whole domain (this is the same as the one we find for each page). It is reported here for convenience.

**===================**
3 - Lead Search endpoint

description:
Returns an object. Find a new lead (a domain name + all the contact information we detect) by technology, language, rank, tech spend. You specify the domain names you already got.

route: /RAPIleA121fSpzA8/

method: POST

parameters: JSON
Let’s start with an example:
{
“and”:“339,312”,
“not”:"",
“lang”:“en”,
“contactfilter”:“e”,
“rankingrange”:“0,20000000”,
“techspentrange”:"",
“already _ explored_dns”:{
domain1.com”:true,
domain2.com”:true
}
}
It means “Give me one new lead (=a domain) which is using Shopify (id 339) AND Hello Bar (id 312) at the same time, in English (“lang”: “en”), that has at least one email address (“contactfilter”:“e”) in the top 20M (“rankingrange”:“0,20000000”) which is not “domain1.com” nor “domain2.com”.”

More explanations on the parameters:
“and”: Comma separated string of technology ids: it means search for websites using technology 1 AND technology2 AND… It can be one id only.
“not”: Comma separated string of technology ids. It means exclude websites using this technology(ies). Can be empty string.
“lang”: Language filter. We support English (en), Spanish (sp), Portuguese (po), French (fr), German (de), Danish (da), Dutch (nl), Italian (it). You can leave it empty string.
“contactfilter”: One or several letter(s). “e” means that the result (lead or website) must have at least an email address. “f” means it must have at least one Facebook link… etc. We support “e” (email address), “t” (phone number), “f” (Facebook), “k” (LinkedIn), “i” (Instagram), “w” (Twitter) and “y” (YouTube). Can be empty if you don’t care about what contact information of the result.
“rankingrange”: Worldwide domain rank RANGE filter. ‘0,1000000’ means the result must be in the top 1M domains. ‘1000000,1000000000’ means it must be beyond the top 1M. Format: Empty string or two consecutive comma separated integers in ascending order (‘0,1000000’ or ‘2000000,50000000’). Can be empty if you don’t care about the ranking of the resulting domain.
“techspentrange”: Works like the “rankingrange” parameter. But for the estimated monthly tech spend. For example, ‘0,100’ means the estimated monthly tech spend must be between USD 0 and USD 100. Can be empty if you don’t care about the tech spend of the resulting domain.
“already _ explored_dns”: The keys in the ‘already _ explored _ dns’ must be domain names without http(s)// nor any slash. And the values must simply be the Boolean value ‘true’. This object lets you set what leads (=domain names) you ALREADY have in order to get a new one.

result:
Example:
“leads”:{
example.com”:{…}
}
“lead _ count”:1
"already _ explored _ dns":{…}
“dns _ scanned”:1

Explanations on how to read that:
The result is an object.
“leads” is the resulting domain name + all the data about this domain name. Please refer to documentation on the second endpoint “Domain Lookup endpoint”. The object is the same.
“lead _ count” is simply 0 or 1. Meaning 0 lead found or 1 new lead found.
“already _ explored _ dns” is the object containing domain names we’ve explored. We recommend you maintain your own “already _ explored _ dns” client-side to search for multiple unique leads.
“dns _ scanned” is the number of domains we’ve scanned. Just for your information.

Do you need help on anything? Do you have a feedback?
We’re listening to you! Feel free to email us at support@findmassleads.com. We’ll be happy to help 😃

Followers: 3
Resources:
Product Website
API Creator:
Rapid account: Findmassleads
findmassleads
findmassleads
Log In to Rate API
Rating: 1 - Votes: 1