Why connect themThe IP Blacklist 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 buildWorkflows 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
TemplatesReady-made ideas.
Incoming webhook with IP address Fetch IP blacklist lookup → return isIPBlacklisted, threatLevel, and inbound.found via webhook responseIP Blacklist Check Webhook Service
Build a microservice that checks IPs against blocklists and returns threat status via webhooks.
Incoming webhook with transaction data Fetch IP blacklist lookup → if isIPBlacklisted, fire alert webhook with ipAddress, threatLevel, and inbound.descriptionBlacklist Alert Webhook
Process incoming events and fire alert webhooks when transactions originate from blacklisted IPs.
SetupConnect 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 IP Blacklist 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 ipAddress) 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/ipblacklistlookup 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.ipAddress 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/ipblacklistlookup 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.ipAddress }}.
- 4
Execute & activate. Execute manually to verify, then activate the workflow for production.
The payloadWhat Webhooks receives.
ipAddress"185.220.101.1"
isIPBlacklistedtrue
inboundfound, description
outbound—
threatLevel"high"
ipDetailsip, country, region, timezone, city, coordinates, countryName, regionName, postalCode, continent, continentName, accuracyRadius