How to Integrate an API w/ Clay

Using API Ninjas to find insights from DNS records

Hey, Claymakers!

I had no idea how to connect APIs before working at Clay.

Since then, I’ve learned, and it’s been a big unlock for creativity and what I’m able to accomplish within Clay.

For example, you can use a DNS record to gain some pretty cool insights on a company’s hosting infrastructure:

  • Check the IP address - if it falls within a specific range, then it’s likely that web traffic is being sent to an on-premise environment. Combining this is with knowledge with their tech stack, it can tell you if they have a hybrid cloud environment.

  • Check A records - if you find multiple A records, then this would point to hosting in multiple regions. You can also figure out if there are multiple geographic regions, and where those are.

  • MX records - this can show you if email is handled in-house or by a third party provider.

  • NS (Name Server) records - this can point to whether the company is using specialized DNS or CDN providers.

A really cool use case of this is from Abnormal Security (unicorn email security provider).

One of their signals is to look at the email provider. Hackers typically execute email attacks within 3 months of a change. So, they use this knowledge to prioritize these accounts and educate the customer.

So… let’s dive in to how to integrate an API: API Ninjas

API Ninjas

The site has 81 APIs that you can pull from. Some of these are free and others you need a paid subscription.

We’ll be using the “DNS Lookup”. But, check that out… they even have Face Detection available.

Step 1: API Ninjas Documentation

You’ll want to do 2 things first:

  1. Find the API documentation page

  2. Get your API key from your account page

1. Documentation Page

We’ll need the following:

  • API Request URL (top left in green)

  • How to input data into the that URL (top right in green)

  • Headers (this is how you’ll pass your API key to the API)

GET requests = used to retrieve data from a specified resource without modifying it.

POST requests = used to submit data to be processed by the specified resource, typically to create new records.

PUT requests = used to update existing resources with new data.

DELETE requests = used to delete a specified resource

PATCH requests = used to partially modfiy an existing record

2. API Key

OK. Now you have everything to pull it all together…

Step 2: Add the HTTP API Enrichment

Step 3: Fill out HTTP API

Now connect everything like below:

Step 4: Run a Column to Test API

200 = successful API run

Around the Kiln

Billboards at SaaStr & Dreamforce

No Need for Job Changer Point Solutions

We can track these changers for you and find new info. Now with confidence levels, and of course, transparency, flexibility, and control.

Clay for SDRs & SDR Leaders - Join the Live Webinar

Image preview

A good reminder

No alternative text description for this image

That’s a wrap!

If you like this content, I also share shorter form stuff on LinkedIn. Would love to connect with you: https://www.linkedin.com/in/alexlindahl/