Subdomain Finder API + Webhooks Integration

Why connect them

The Subdomain Finder 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.

Incoming webhook with domain Fetch subdomains → return host list, records, count, and totalFound via webhook response

Subdomain Discovery Webhook Service

Build a subdomain discovery microservice that returns enumeration results via webhooks.

Scheduled daily trigger Fetch subdomains → compare with previous scan, fire webhook with new host entries if count changed

New Subdomain Alert Webhook

Trigger a webhook alert when new subdomains are detected for monitored domains.

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 Subdomain Finder 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 rootDomain) 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/subdomainfinder 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.rootDomain 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/subdomainfinder 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.rootDomain }}.
4
Execute & activate. Execute manually to verify, then activate the workflow for production.

The payload

What Webhooks receives.

rootDomaindomain, records

subDomainsarray of 47

count47

totalFound47

Subdomain Finder API + Webhooks