DNS Lookup API + Webhooks

Send the response straight into Webhooks — connected through Zapier, Make, or n8n, no code required.

Get your free API key→

WhenWebhooksReceive webhook

trigger

RunDNS Lookup APIReturns the response

action

ThenWebhooksSend webhook

Why connect them

The DNS Lookup API in Webhooks.

Webhooks enable real-time communication between any systems. Connecting APIs with webhooks creates unlimited integration possibilities. Build custom workflows that respond instantly to events from any source.

What you can build

Workflows worth wiring.

Receive data from any system and enrich it with API calls before processing

Build custom notification systems that validate and route incoming data

Create middleware that transforms and validates webhook payloads

Chain multiple APIs together for complex data processing pipelines

Templates

Ready-made ideas.

Webhook received (domain query) Lookup DNS → return records via webhook

Real-time DNS lookup on demand

Receive a domain via webhook, query all DNS records, and return records.A, records.MX, records.NS, and records.TXT to your application.

Scheduled check triggers webhook Lookup DNS → post changes to endpoint

DNS change detection webhook

Periodically query DNS for monitored domains and post a webhook to your endpoint whenever records.A or records.MX values change.

Setup

Connect it in a few steps.

Set up with Zapier

1
Set the trigger. Create a Zap with Webhooks as the trigger app and "Receive webhook" as the event. Connect your account.
2
Add the API action. Add APIVerve as the action, select the DNS Lookup API, and map your trigger data to the request.
3
Send it back. Add a second Webhooks action for "Send webhook" and map the returned fields (like domain) into it.
4
Test & turn on. Test the Zap with real data to confirm the mapping, then turn it on.

Set up with Make

1
Add the trigger. Create a scenario and add a Webhooks module set to "Receive webhook". Authenticate your account.
2
Call the API. Add an HTTP module pointing at api.apiverve.com/v1/dnslookup with your x-api-key header. Pass the trigger's data as the input.
3
Parse & map. Add a JSON module to read the response, then a Webhooks module for "Send webhook". Map fields like data.domain into place.
4
Activate. Run once to confirm the mapping, then switch the scenario on and set its schedule.

Set up with n8n

1
Add the trigger node. Start a workflow with a Webhooks trigger node for "Receive webhook" and connect your credentials.
2
Add an HTTP Request node. Point it at api.apiverve.com/v1/dnslookup using Header Auth (x-api-key). Feed in the trigger data.
3
Map with expressions. Add a Webhooks node for "Send webhook" and reference the response with expressions such as {{ $json.data.domain }}.
4
Execute & activate. Execute manually to verify, then activate the workflow for production.

The payload

What Webhooks receives.

domain"google.com"

recordsA, AAAA, CNAME, MX, NS, PTR, SRV, SOA, TXT, CAA

ttlA, AAAA, CNAME, MX, NS, PTR, SRV, SOA, TXT, CAA

summaryhasIPv6, hasMailServers, hasSPF

Webhooks + DNS Lookup API FAQ

What are webhooks and how do they work with APIs?

Webhooks are HTTP callbacks triggered by events. They receive data from one system, which you can then process through APIs before sending to another destination.

How do I validate incoming webhook data?

Use automation platforms to receive webhooks, extract data fields, validate them with external APIs, and route based on validation results.

Can I transform webhook data before sending to APIs?

Yes. Automation platforms provide data transformation steps. Map, filter, and format incoming webhook data before calling external APIs.

DNS Lookup API + Webhooks

The DNS Lookup API in Webhooks.

Workflows worth wiring.

Ready-made ideas.

Real-time DNS lookup on demand

DNS change detection webhook

Connect it in a few steps.

What Webhooks receives.

Webhooks + DNS Lookup API FAQ

Connect the DNS Lookup API to Webhooks. One key, no code, live in minutes.

Scaling up?