Repository navigation
Security API Catalog and Integration Cookbook
Reviewed: November 2, 2026. Scope: APIs relevant to authorized OSINT, vulnerability prioritization, incident response, external asset discovery, web/API testing and data pipelines.
Documentation ยท OSINT ยท Incident response ยท Data ingestion ยท Repository
Important
The list below is curated from public-apis/public-apis, not a full import. Listing an API does not establish live availability, a free tier, permission to scan, or suitability for customer information. Pricing, credentials, quotas, schemas, product restrictions and privacy terms can change. Check official provider terms and docs before use. Never submit customer data or private indicators to public scan/sandbox services without approval.
The source directory is MIT licensed; each service has its own usage restrictions. Descriptions, triage steps and request examples below are independently written and linked to official providers. When the upstream directory points to a paid wrapper, obsolete feed or unclear authentication model, prefer the canonical source.
Existing in repo means PNWC docs/scripts already reference the providerโnot that a live API test passed. Reference means a candidate for a future integration, not that a key, scheduler, or connector exists. Official companion means an authoritative API/feed included alongside the directory's entry.
| API | Security workflow | Integration status | Official documentation |
|---|---|---|---|
| AbuseIPDB | IP reputation and reported abuse context | Existing OSINT script; key required | API v2 |
| AlienVault OTX | Threat pulses and IOC context | Existing OSINT script; key-based workflows | OTX API |
| VirusTotal | Existing domain, IP and file-hash reputation | Existing OSINT script; key and restrictive quota | API v3 |
| URLhaus | Malware-distribution URLs and optional IDS feeds | Existing OSINT script; current Auth-Key rules require review | Community API |
| urlscan.io | Search existing website scans and associated indicators | Existing OSINT script; API key for normal use | API docs |
| GreyNoise Community | Assess background internet scanning versus targeted activity | Reference; limited unauthenticated access | Community API |
| Google Safe Browsing | Known unsafe URL verdicts for permitted use cases | Reference; API key and terms | Official docs |
| Hybrid Analysis | Malware sandbox report enrichment | Reference; key and upload/data-handling restrictions | API v2 |
Existing-script caveat: threat_feed_check.sh currently uses an unauthenticated POST https://urlhaus-api.abuse.ch/v1/. The current URLhaus community documentation requires an Auth-Key for API/dataset use. Do not treat its missing/error response as a clean verdict. Authenticate and retest that script separately before production use; this documentation change does not alter live code.
Related: OSINT toolkit ยท Threat intelligence AgentFlow ยท SIEM ยท IDS/IPS.
| API | Security workflow | Integration status | Official documentation |
|---|---|---|---|
| Shodan | Internet-visible services and in-scope device inventory | Existing catalog; key / plan | API |
| Censys | Hosts, certificates and exposed services | Existing catalog; key / plan | API |
| BinaryEdge | Supplemental attack surface and host context | Existing catalog; key / plan | API v2 |
| SecurityTrails | Current/historical DNS and domain relationships | Existing catalog; key / plan | Documentation |
| EmailRep | Email reputation context (not identity proof) | Existing catalog; check current quota/access | Documentation |
| Have I Been Pwned | Breach-awareness and authorized domain exposure auditing | Existing catalog; key/eligibility by endpoint | API v3 |
| IPinfo | ASN, network owner, approximate location | Reference; public/paid endpoints vary | Developer docs |
| Cloudflare DNS over HTTPS | DNS record lookups through read-only DoH resolver | Official companion; no key for resolver | DoH guide |
Use passive, authorized context only. Geolocation is approximate, an exposed socket is not automatically a vulnerability, and correlation is not proof of a person's identity.
Related: domain/IP recon ยท email OSINT ยท web security.
| API | Security workflow | Integration status | Official documentation |
|---|---|---|---|
| National Vulnerability Database (NVD) | CVE/CPE queries and severity/product context | Official API 2.0; anonymous low-rate / optional key | CVE API |
| CISA Known Exploited Vulnerabilities | Prioritize known-exploited CVEs over score-only queues | Official public JSON feed, not the directory's third-party RapidAPI wrapper | CISA KEV |
| GitHub Global Security Advisories | Package/ecosystem vulnerabilities (GHSA) | Official companion; public read API | GitHub REST |
| GitGuardian | Detect exposed secrets in repositories you may inspect | Reference; credentials and data-handling review | API docs |
| CRXcavator | Risk review for browser extensions | Reference; key | API docs |
Decision workflow: verify installed product/version and exposure โ read vendor guidance โ correlate NVD/GHSA โ mark KEV where present โ determine patch/mitigation priority and ownership. KEV inclusion means exploitation has been observed somewhere, not that this particular asset was compromised.
Related: Incident response ยท Cloud ยท Containers.
| API | Security workflow | Integration status | Official documentation |
|---|---|---|---|
| APIs.guru | Find OpenAPI specifications for owned/lab API contract testing | Reference; public catalog | API directory |
| Postman Echo | Synthetic HTTP request/response testing | Reference; public demo service | Echo docs |
| Cloudflare | Manage authorized DNS/edge configuration via scoped tokens | Reference; token and plan | Official API |
| Bitwarden | Vault/organization governance (appropriate deployment) | Reference; OAuth and plan/deployment conditions | API guide |
| Bugcrowd | Approved bounty/disclosure report lifecycle | Reference; program credentials | Official API |
| HackerOne | Authorized vulnerability reporting/triage | Reference; program credentials | API |
A published OpenAPI specification is not permission to test the provider's service. Do not submit sensitive requests to public echo endpoints. Separate report-management APIs from scanning tools.
Related: Web app methodology ยท Cloud ยท Data Engineering.
Illustrative commands use public reference records; they have not been executed against every current version/service. Requires curl and jq. Observe provider quotas. Inspect HTTP status and JSON error objects before making a verdict.
# Public example domain; Cloudflare JSON DoH format.
curl -fsS --get -H 'accept: application/dns-json' \
--data-urlencode 'name=example.com' --data-urlencode 'type=A' \
'https://cloudflare-dns.com/dns-query' | jq '.Answer // []'
# GreyNoise anonymous community quota is limited; 429 is not a benign verdict.
curl -fsS 'https://api.greynoise.io/v3/community/8.8.8.8' | jq .curl -fsS --get --data-urlencode 'cveId=CVE-2021-44228' \
'https://services.nvd.nist.gov/rest/json/cves/2.0' \
| jq '[.vulnerabilities[]?.cve.id]'
curl -fLsS --retry 2 \
'https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json' \
-o kev.json
jq '{catalogVersion, dateReleased, count}' kev.json
jq -r '.vulnerabilities[] | select(.cveID=="CVE-2021-44228") | .vulnerabilityName' kev.json
curl -fsS -G -H 'Accept: application/vnd.github+json' \
--data-urlencode 'cve_id=CVE-2021-44228' \
'https://api.github.com/advisories' | jq '.[].ghsa_id'Provide keys through an approved secrets manager/environment, never
include real values in committed files, logs or screenshots. Caution:
interpolating keys into curl -H arguments can expose them to local process
inspection on some systems; for production use, prefer a protected
curl --config file (mode 0600), a credential-aware client library or a
secret-injection mechanism that avoids command-line arguments. Both queries
below use Google's public resolver IP only as a synthetic example.
: "${ABUSEIPDB_API_KEY:?configure in approved secret store}"
: "${VT_API_KEY:?configure in approved secret store}"
curl -fsS -G -H "Key: ${ABUSEIPDB_API_KEY}" \
-H 'Accept: application/json' \
--data-urlencode 'ipAddress=8.8.8.8' \
--data-urlencode 'maxAgeInDays=90' \
'https://api.abuseipdb.com/api/v2/check' \
| jq '{ip:.data.ipAddress, reports:.data.totalReports}'
curl -fsS -H "x-apikey: ${VT_API_KEY}" \
'https://www.virustotal.com/api/v3/ip_addresses/8.8.8.8' \
| jq '{id:.data.id, reputation:.data.attributes.reputation}'curl -fsS -G --data-urlencode 'case=synthetic-lab' \
'https://postman-echo.com/get' | jq '.args'
# Inspect a known-good local OpenAPI document. Do not auto-execute methods.
jq '{version:.openapi, paths:(.paths | keys)}' ./approved-openapi.json- Scope and privacy: record owner, permitted indicator/data types, and whether request data may be disclosed to a third party. A hash is not necessarily anonymous.
-
Credentials: use scoped/rotated keys; never commit an actual
api_keys.conf. Implement least privilege and redact headers from logs. -
Transport and quota: TLS verification, timeout, 429/
Retry-Afterhandling, bounded exponential backoff, checkpointed pagination, response-size caps and caching. - Provenance: retain request timestamp (UTC), provider name, response status, schema/version, source indicator, source reliability and lookup result separately.
- Error handling: unavailable, unauthorized, throttled, malformed and unknown are not clean/benign. Do not auto-block or delete assets based on one provider score.
- Validation: use synthetic data first; get consent before public site submissions or sample uploads. Test rate limits, schema drift, conflicting intelligence and recovery.
- SIEM design: normalize enrichment outputs, correlate with local alerts, add human-review gates, document retention. Wazuh should not ingest raw API keys.
Suggested future workflow (not deployed): in-scope inventory โ passive exposure/DNS queries โ NVD + GHSA + KEV prioritization โ approved reputation lookups โ time-stamped JSON โ SIEM triage and analyst review.
- Source catalog: public-apis/public-apis, MIT license. Provider APIs have separate terms.
- Priority official sources: NVD, CISA KEV, URLhaus, VirusTotal, urlscan.io, Cloudflare DoH, GreyNoise.
- Verification limits: providers/doc links were reviewed selectively; API live responses, costs, quota entitlements and data-processing terms were not tested across every provider. No account was created, key used, API scheduled, file uploaded or client asset scanned for this change.
๐ Source: Documentation/security-public-api-catalog.md | โ๏ธ Suggest an edit | โฌ
๏ธ Back to Technical Guides & Cheat Sheets
- ๐บ๏ธ Browse by Topic
- ๐ All Repository Files
- ๐งญ Learning Paths
- ๐ Master Guide
- ๐ค Glossary
- โ๏ธ Legal & Disclaimer
๐ Foundations & Learning
๐ก๏ธ Defense & Investigations
- Incident Response
- Open Source Intelligence (OSINT)
- Reverse Engineering
- Operations Security (OPSEC)
- Compliance
โ๏ธ Platforms & Infrastructure
๐ก Hardware, Wireless & Field Projects
- PNWC Cyberdeck
- Hardware Testing
- Hardware Hacking
- Software-Defined Radio
- Wardriving
- uConsole
- Space Security
๐งฐ Assessment & Field Reference
๐ฆ Downloads & Project Resources
๐๏ธ Additional Topics