IP Blacklist Lookup API + GitHub Integration

Why connect them

The IP Blacklist Lookup API in GitHub.

GitHub is where developers build software together. Connecting APIs to GitHub enables automated code workflows, intelligent issue management, and CI/CD enhancements. Supercharge your development processes with external data.

What you can build

Workflows worth wiring.

Automatically validate URLs in README files for broken links

Check DNS configurations when deploying to new environments

Verify SSL certificates as part of deployment pipelines

Create issues automatically when external monitoring detects problems

Templates

Ready-made ideas.

New issue created in GitHub Fetch IP blacklist lookup for reported IP → add isIPBlacklisted, threatLevel, and inbound.description as issue comment

IP Blacklist Context in GitHub Issues

Enrich GitHub security issues with IP blacklist status and threat details for incident triage.

New issue created in GitHub Fetch IP blacklist lookup → add label based on threatLevel and comment with ipDetails.countryName

Automated Threat Triage in GitHub

Automatically label and enrich GitHub security issues based on the reported IP's threat level.

Setup

Connect it in a few steps.

Set up with Zapier

1
Set the trigger. Create a Zap with GitHub as the trigger app and "New issue" 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 GitHub action for "Create issue" 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 GitHub module set to "New issue". 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 GitHub module for "Create issue". 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 GitHub trigger node for "New issue" 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 GitHub node for "Create issue" 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 payload

What GitHub receives.

ipAddress"185.220.101.1"

isIPBlacklistedtrue

inboundfound, description

outbound—

threatLevel"high"

ipDetailsip, country, region, timezone, city, coordinates, countryName, regionName, postalCode, continent, continentName, accuracyRadius

IP Blacklist Lookup API + GitHub