Summary
The integration between Skrapp and Clay allows you to enrich Clay leads with verified professional email addresses and key company data such as industry, headquarters location, revenue, and employee count. Additionally, it automates the email verification process for existing leads.
Skrapp HTTP APIs
1. Email Finder:
Enriches leads with verified business emails.
- Feature: Email Finder
- API Documentation: API
2. Email Verifier:
Verifies email addresses in Clay tables.
- Feature: Email Verifier
- API Documentation: API
3. Company Data Search:
Provides key company data such as industry, HQ location, revenue, and headcount.
- Feature: Company Data Search
- API Documentation: API
Common Skrapp HTTP API Clay Integration Steps
1- Create a Clay table.
2- Add lead data such as names and company names or websites.
3- Add a new column by clicking on "Add Column," then select "Add Enrichment."
4- Search for API in the search bar and select "Clay > HTTP API."
5- Choose the appropriate Skrapp API depending on the data you wish to enrich and follow subsequent steps detailed in the next section:
-
- Email Finder API
- Email Verifier API
- Company Data Search API
For general information on how to integrate HTTP APIs with Clay: HTTP API Integration with Clay
Steps for Skrapp HTTP API Integrations
- Get the API key from your account settings under "API Access Key" at Skrapp Account Settings.
-
Include the API key in the header of your requests as
X-Access-Key: {Your API Key}
. - For more information on how to authenticate to a Skrapp API: Skrapp API Authentication
Note: Each Skrapp HTTP API integration with Clay should follow the common steps detailed above.
1. Email Finder API
The Email Finder API enriches leads with professional email addresses based on names and company domains or company names. The following steps outlines the integration process with Clay:
API Details:
-
Endpoint:
https://api.skrapp.io/api/v2/find
- Version: V2
-
Parameters:
-
firstName
(Text): Lead's first name -
lastName
(Text): Lead's last name -
fullName
(Text): Full name of the lead -
domain
(Text): Company domain (e.g., company.com) -
company
(Text): Company name (e.g., company)
-
-
Headers:
X-Access-Key: {Your API Key}
-
Rules:
- Either
fullName
orfirstName
andlastName
must be provided - Either
company
ordomain
must be provided
- Either
-
Response:
- Type: JSON
- Field:
email
(professional email)
Integration Steps:
1- Add a Clay table column named “Email.”
2- Follow the common steps detailed above to create a new HTTP API column.
3- Set the method to GET and the endpoint to: https://api.skrapp.io/api/v2/find
.
4- Add query parameters by linking them to the appropriate Clay table columns.
5- Add your API key in the X-Access-Key
header.
6- Set the "Field Path to Return" to email
(path to email in the API response).
7- Save, then select to run for rows or not.
8- Edit the Clay "Email" column to reflect the response from the HTTP API.
Your table is now enriched with professional email addresses using Skrapp.
2. Email Verifier API
The Email Verifier API verifies professional email addresses and provides the following statuses:
- Valid: Confirmed as valid and reachable.
- Catch-All: Potentially risky, but reachable.
- Invalid: Unreachable due to various issues (e.g., inactive domain, non-existent recipient).
- Unknown: Status unresolved due to server issues.
For more details: Email Verification Statuses
API Details:
-
Endpoint:
https://api.skrapp.io/v3/verify
- Version: V3
-
Parameters:
-
email
(Text): Email address to verify
-
-
Headers:
X-Access-Key: {Your API Key}
-
Response:
- Type: JSON
- Field:
email_status
Integration Steps:
1- Add a Clay table column named Email Status or similar.
2- Follow the common steps detailed above to create a new HTTP API column.
3- Set the method to GET and the endpoint to: https://api.skrapp.io/v3/verify
.
4- Add query parameters by linking the email
parameter to the Clay table's "Email" column.
5- Add your API key in the X-Access-Key
header.
6- Set the "Field Path to Return" to email_status
.
7- Save, then select to run for rows or not.
8- Edit the "Email Status" column to reflect the response from the HTTP API.
Your table is now enriched with the email verification statuses provided by Skrapp.
3. Company Data Search API
The Company Data Search API provides key company data such as:
- Complete name
- Domain
- Type (Public/Private)
- Industry
- Revenue range
- Employee count
- Geographic area (city, country, postal code)
- LinkedIn URL, Crunchbase URL, and more
API Details:
-
Endpoint:
https://api.skrapp.io/lwh/company/search
-
Parameters:
-
kw
(Text): Company domain or name
-
-
Headers:
X-Access-Key: {Your API Key}
-
Response:
- Type: JSON
- Field:
results
(contains the company information)
Integration Steps:
1- Add a Clay table column named Company Industry (or any other field).
2- Follow the common steps detailed above to create a new HTTP API column.
3- Set the method to GET and the endpoint to: https://api.skrapp.io/lwh/company/search
.
4- Add query parameters by linking the kw
parameter to the Clay table's Domain or Company Name column.
5- Add your API key in the X-Access-Key
header.
6- Set the Field Path to Return to results
.
7- Save, then select to run for rows or not.
8- Edit the "Company Industry" column to reflect the response from the HTTP API.
Your table is now enriched with company industry data, and you can repeat the process for other fields such as revenue or employee count.
Integrating Skrapp’s powerful APIs with Clay improves your lead management process by automatically enriching and verifying contact and company data. Whether you are looking to find professional emails, verify email addresses, or gather key company insights, this integration streamlines your workflow and improves your data accuracy.
You can watch a live demonstration of how to connect Clay with the Skrapp Email Finder API:
For additional guidance or if you encounter any issues during the integration process, feel free to submit a support request at Skrapp Support. Our support team is ready to assist you with any queries or concerns.
Related to
Comments
0 comments
Please sign in to leave a comment.